Connect AI agents to Blog2Social and automate social media content workflows via MCP.
Scored across 10 tools
Each tool targets a distinct resource and action (connections vs networks vs posts vs videos vs credits), and descriptions explicitly cross-reference boundaries, e.g. account.overview says to use posts.insights for per-post analytics and connections.list says to use networks.list for available networks. The only mild overlap is account.overview vs credits.balance, but one is aggregated usage and the other is a point-in-time balance, so selection is unambiguous.
All tools use a consistent namespaced dot convention (namespace.action) such as connections.add, networks.properties, posts.publish_post, which makes ownership of each tool obvious at a glance. Minor deviation: some actions are verbs (add, list, remove, publish_post) while others are nouns (overview, balance, properties, insights, status), so the pattern is not perfectly uniform.
Ten tools is well within a healthy range and each earns its place: connection lifecycle, network discovery, capability lookup, credits, publishing, video polling, and insights. There is no redundancy or filler.
The publish workflow is covered end to end: networks.list → networks.properties → connections.add/list → credits.balance → posts.publish_post → videos.status → posts.insights. However, there is no scheduling/draft support (explicitly called out as unsupported), no post listing/deletion, so agents cannot manage previously published content.
Use this tool when the user asks for an account-level overview of Blog2Social API credit usage.
It returns the current credit balance and aggregated usage totals grouped by day, endpoint, and social network.
The optional days parameter must be an integer between 1 and 30. If omitted, the endpoint default applies.
The results describe aggregated account usage. They do not provide performance metrics or analytics for individual published social media posts. Use posts.insights for individual post performance.
Inputs: days. Returns: data
Use this tool when the user wants to connect an account on a selected social network. It starts OAuth authorization and returns an auth_link that the user must open and approve. It requires network_id and network_type_id obtained from networks.list. network_type_id 0 means profile, 1 means page, and 2 means group. The connection is not complete until the user finishes authorization. Pinterest also requires an active custom app assigned to the API service.
Inputs: network_id (required), network_type_id (required), language. Returns: data
Use this tool to retrieve the social media accounts connected to the authenticated Blog2Social user. It returns the network, account type, display name, and client_user_network_id for each connection. Use it to identify the correct connected account before publishing or disconnecting it. It does not list networks available for connection. Use networks.list for that purpose.
Inputs: no named parameters. Returns: data
Use this tool only when the user explicitly asks to disconnect a specific connected social media account. It removes the connection identified by client_user_network_id from the authenticated Blog2Social user. This is a destructive action. After disconnection, the account cannot be used for publishing until it is connected again through connections.add.
Inputs: client_user_network_id (required). Returns: data
Use this tool to retrieve the current credit balance of the authenticated Blog2Social API account. Use it when the user asks about available credits or before an action that may consume credits, such as publishing or retrieving post insights.
It returns the current available credit balance. It does not provide individual post analytics, account usage statistics, or billing details. Publishing is not possible when the balance is zero.
Inputs: no named parameters. Returns: data
Use this tool to retrieve the social networks available to the authenticated Blog2Social API user. It returns network IDs and supported account types, including profiles, pages, and groups. Use it before connecting an account or when valid network IDs and account types are required. It does not list connected accounts or start authorization. Use connections.list to retrieve connected accounts and connections.add to start connecting an account.
Inputs: no named parameters. Returns: data
Use this tool to retrieve publishing requirements and capabilities for a specific social network and account type. It returns available publishing formats and restrictions, such as supported media formats, video support, and character limits. Use it before publishing to check whether the requested content is supported. Requirements and capabilities vary by network and account type. This tool does not publish content or guarantee acceptance by the social network.
Inputs: no named parameters. Returns: data
Use this tool when the user asks for performance metrics or analytics for your own published social media post.
It retrieves the latest available performance insights and associated credit information for the specified published post.
It requires the public publish_url returned after a successful posts.publish_post operation. It works only for supported social networks and account types with tracking enabled.
Available metrics depend on the social network, account type, published post, tracking availability, and data returned by the endpoint. Not all metrics are available for every post or network.
Report only metrics actually returned by the server. Do not interpret missing metrics as zero or invent unavailable performance data.
The request may deduct credits according to the account and network pricing. Consider the credit cost before making the request.
Inputs: post_url (required). Returns: data
Use this tool when the user explicitly asks to publish social media content immediately. It publishes the supplied b2s_posts to the connected social media account identified by client_user_network_id. This action publishes content directly and does not create a draft or schedule a post for later publication.
postFormat must be:
0 for text or link
1 for image
2 for video
Image and video posts require mediaObjects with the matching IMAGE or VIDEO type and a publicly accessible HTTP or HTTPS URL.
Check networks.properties before publishing to verify the requirements for the selected network and account type.
The response can include:
publish_url for retrieving post performance insights with posts.insights
video_token for checking video publication status with videos.status
Evaluate all returned error fields, including b2s_error_code. Do not automatically retry uncertain publishing operations.
Inputs: b2s_posts (required), client_user_network_id (required). Returns: data
Use this tool after a video post has been submitted through posts.publish_post and the response contains a video_token.
It checks whether video publication has finished and returns the status for each target account.
Possible statuses:
pending
failed
successful
The response may include a publish_url after successful publication.
Use the video_token returned by posts.publish_post. If the status is pending, check again later. Do not retrieve post insights until successful publication has been confirmed and a publish_url is available.
Inputs: video_token (required). Returns: object
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Connect any AI agent to 11+ social platforms: schedule, publish & track posts via hosted MCP.
Post and schedule to TikTok, Instagram, YouTube, Facebook, LinkedIn, X, Threads and Bluesky from your AI agent. Video included, you approve every post, and MCP is on the free plan.
Connect AI agents to Social Champ: manage channels, posts, AI content, queue, and approvals.
Agent-first social media publishing, scheduling, analytics, and unified inbox API + 16-tool MCP server across 18 social platforms (X, LinkedIn, Instagram, YouTube, TikTok, Threads, Bluesky, Reddit, Telegram, Discord, Mastodon, Facebook, Pinterest).
Add one secure layer between your agents and this server.
