Skip to main content
Glama

Social0

publish_post

Destructive

Publish an existing unpublished Social0 draft (or scheduled post) immediately to connected platforms. Returns a tracking ID to monitor progress. Example: 'Publish my latest draft to Twitter.'

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": {
      "post_id": "<post_id>"
    },
    "name": "publish_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
mediaNoOptional media IDs from upload_media to attach before publishing
post_idYesDraft or scheduled post ID to publish immediately
platformsNoOptional subset of platforms/account IDs to publish to
platform_optionsNoAdvanced per-platform settings. Supports content/caption and media per platform, plus pinterest board_id/title/link/create_board, tiktok title/privacy/draft/comment/duet/stitch/commercial/AI flags, instagram cover_image_url/trial_reel, youtube title, and x/twitter_x madeWithAi/paidPartnership.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the mutation risk is signaled structurally. The description adds value by noting it targets live connected platforms and returns a tracking ID for monitoring (important since no output schema exists), but it never warns that publishing to live social platforms is publicly visible and not undoable, nor explains what happens to the draft afterward.

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?

Three short sentences, front-loaded with the action and scope, then the return value, then a concrete example. Little waste, though the example sentence adds less than an explicit alternative-tool pointer would have.

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

Completeness3/5

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

For a destructive, non-idempotent publish tool with a nested platform_options object, the description covers the core action and return handle but omits failure behavior (what happens if a platform rejects the post), whether the draft is consumed, and how it differs from publish_now. Adequate but with meaningful gaps.

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

Parameters3/5

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

Schema coverage is 100%, and the schema itself documents media, post_id, platforms, and even the nested platform_options per-platform flags in detail. The description's only added meaning is the 'attach before publishing' intent and the illustrative 'Publish my latest draft to Twitter' example hinting at platforms narrowing — marginal over the schema, so the baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource: publishing an existing draft or scheduled post immediately to connected platforms, plus the return value (tracking ID). It scopes the input to pre-existing drafts, but with a sibling named publish_now it never clarifies the distinction between the two similarly-named tools, so an agent cannot fully disambiguate from the name and text alone.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: use this when you have an unpublished draft or scheduled post and want it live now. There is no explicit 'use publish_now instead when…' or 'use schedule_post instead when…' routing, and no prerequisites such as connected-account requirements, even though publish_now and schedule_post sit alongside it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.