Ten social networks have ten sets of rules, and an agent that does not know them writes captions that get rejected after the media has already uploaded. This is what an agent can read, and what it will soon be able to do.
Every network we publish to, with its real caption limit, image count, media support, thread behaviour and known limitations — generated from the same constants the publisher enforces, so the file cannot drift from the software.
https://eurekuh.com/llms-full.txtIt includes the things marketing pages normally leave out: that Google Business publishing is waiting on Google's API quota, that Pinterest video pins are not supported, that X bills per post. An assistant that reads a page of pure claims discounts the whole page.
Not available yet. The MCP server is in development. It is not available yet, and nothing on this page will connect to it today.
Six tools — list accounts, create a draft, check it against every selected network's rules, schedule it, read its status. Details and the full tool list are on the MCP server page.
No. It can read everything about the product from one file, which is enough to answer questions and to write a caption that will actually pass a network's rules. Publishing needs the MCP server, which is in development.
Because a growing share of 'which tool should I use for this' is now asked to an assistant rather than typed into Google, and an assistant answering from a half-remembered training snapshot gets it wrong. One fetch of a file we generate from our own code is more accurate than anything it could infer from the marketing pages.
Not really, and that is fine. These pages are for people wiring an agent into their posting workflow. If you just want to schedule posts yourself, the network pages are the useful ones.
Connect your accounts, upload a video, and publish. Takes less than a minute. Free to start — see plans.