Skip to main content
Glama

Publish Social Post

publish_social_post
Destructive

[publish] Publish a draft/scheduled post right now (or retry a FAILED one). platform = ig|fb|tw|tt|yt|li|th|tg|bsky; post_id = _post_id, or pass post_uuid. Goes live on the real platform (tg: into every target chat, one after another).

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": {
      "platform": "<platform>"
    },
    "name": "publish_social_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idNo
platformYes
post_uuidNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false; the description adds real context beyond them by stating the effect is external and irreversible ("goes live on the real platform") and by disclosing Telegram's fan-out behavior ("into every target chat, one after another"), which implies partial-success risk. It omits account/permission prerequisites and what happens if one target chat fails mid-sequence.

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 tight sentences, front-loaded with the action and immediately followed by the two identifier forms and the side-effect warning. The telegraphic "key = value" notation and bracketed "[publish]" tag are slightly cryptic but cost little space.

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

Completeness4/5

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

For a destructive, open-world mutation with no output schema, the definition covers action, identifier forms, platform enumeration, and the live side effect. Remaining gaps—return value, per-target failure behavior on Telegram, and permission requirements—are modest given the annotations already flag destructiveness and non-idempotency.

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 0%, so the description carries the burden and largely does: it enumerates the platform codes (ig|fb|tw|tt|yt|li|th|tg|bsky) that the schema does not, explains post_id is the platform-specific id, and offers post_uuid as an alternative identifier. It stops short of stating whether post_id and post_uuid are mutually exclusive or which takes precedence.

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 ("publish a draft/scheduled post") plus the temporal qualifier "right now," which implicitly separates it from schedule_social_post and create_social_post. The parenthetical "(or retry a FAILED one)" further bounds the operation to two concrete cases.

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 clear when-to-use conditions: for posts already drafted or scheduled that should go live immediately, and for retrying posts in FAILED state. It never names schedule_social_post or create_social_post as the alternative for the deferred/new-post case, so the routing is inferable but not explicit.

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.