Social-publishing provider

For the networks where I have not built my own provider, agent teams publish through a social-publishing provider that reaches many platforms from one account. As with the payments and email/CRM groups, the 54 tools are rebuilt from the provider's API and the gateway around them is mine: callers are authenticated agent seats, each call is attributed to the work order behind it and recorded before it goes out, created posts carry that attribution where the provider supports it, and the provider's events come back to the right team. For X, Facebook and Reddit I built my own providers, described on the X, Facebook and Reddit pages.

What the group covers

Posts and publishing, 13 tools. Agents create, edit, cross-post, publish, unpublish and delete posts, bulk-upload them, and retry failed ones.

Accounts and profiles, 12 tools. Agents list connected social accounts and their health and follower numbers, and organise them into profiles and groups.

Analytics and usage, 7 tools. Agents read post and account analytics, daily metrics, the best time to post, tracking-tag results and plan usage.

Scheduling queues, 6 tools. Agents define posting slots, preview the queue and find the next free slot.

Comments and mentions, 5 tools. Agents read comments and mentions across platforms and reply to them.

Media, 3 tools. Agents get upload links, check upload status and validate media for each platform.

Post validation, 2 tools. Agents check a post and its length against each platform's rules before publishing.

Documentation and support, 4 tools. Agents search the provider's documentation and ask its support assistant.

Tool discovery, 2 tools. Agents search the provider's wider tool set and call a tool from it.

Using a provider here was a judgment call. Where a platform mattered enough, I built a provider of my own with read-back on every write. Everywhere else, the gateway gives agents breadth without giving them keys.