Blog2Social - Social Media Publishing

Publish a post immediately

posts.publish_post

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "client_user_network_id": "<client_user_network_id>",
      "b2s_posts": "<b2s_posts>"
    },
    "name": "posts.publish_post"
  }
}

Input Schema

Name	Required	Description	Default
`b2s_posts`	Yes	One or more posts to publish to the selected account. Use postFormat 0 for text or links, 1 for images, and 2 for videos; image and video posts require mediaObjects.
`client_user_network_id`	Yes	Connected social media account ID returned by connections.list. All posts in b2s_posts are published to this account.

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 30, 2026

TDQS

A4.6/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations by warning against automatic retries on uncertain publishes (critical given idempotentHint=false and openWorldHint=true), instructing inspection of b2s_error_code, and noting the operation is direct/irreversible in the sense that no draft is produced. This is exactly the operational context annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the usage gate and the non-scheduling clarification, then structured bullet sections for format codes and response fields. The postFormat enumeration largely duplicates the schema consts, a minor redundancy, but nothing is padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, yet the description still helpfully routes publish_url to posts.insights and video_token to videos.status, which is the missing link an agent needs after a publish. Combined with annotations and full schema coverage, nothing needed to call this correctly is absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description adds meaning by mapping postFormat values to post types and stating that image/video posts require mediaObjects with matching type and a public HTTP(S) URL. It also explains that client_user_network_id comes from connections.list, which the schema hints at but the description reinforces operationally.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('publishes the supplied b2s_posts to the connected social media account') and explicitly contrasts with drafting or scheduling, which no sibling offers. An agent can distinguish this from posts.insights or videos.status without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a clear invocation gate ('when the user explicitly asks to publish ... immediately') and a prerequisite step (check networks.properties first). It says what it is not (not a draft, not a scheduled post) but never names the sibling tool an agent should use for scheduling instead, leaving that inference to the reader.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Blog2Social - Social Media Publishing tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.