Skip to main content
Glama

Publish a post now

publish_post_now
Destructive

Publishes a saved post to its networks right away. A network that can't take it (connection broken, or a check it fails, like YouTube without a video) is left out and listed in skipped; the rest still go. Counts toward the plan's post allowance (one per network). Publishing takes about a minute; get_post shows each network's result.

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_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYesThe post id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, but the description adds genuinely non-obvious behavior: per-network partial failure with failures returned in a "skipped" list while the rest still publish. It also discloses that the call consumes one post from the plan allowance per network and takes roughly a minute, which an agent needs to avoid treating a failure as total or retrying blindly.

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

Conciseness5/5

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

Three tight sentences, front-loaded with the action, then partial-failure behavior, then cost and result-retrieval. No filler and nothing repeated from the title.

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?

For a one-parameter, non-idempotent mutation with no output schema, the description covers everything material: what happens on partial failure, that skipped networks are reported, the allowance cost, the latency, and where to check per-network results via get_post.

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% for the single post_id parameter, so the baseline applies. The description adds only the mild constraint that the post must already be "saved" rather than newly composed; it gives no format or validity details beyond the schema.

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?

"Publishes a saved post to its networks right away" gives a specific verb (publishes), resource (a saved post), and scope (all its networks). "Right away" implicitly separates it from schedule_post and create_post, but no sibling is named outright, so the differentiation is inferred rather than stated.

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: this is the immediate-publish path for an already-saved post, versus scheduling or creating. There is no explicit when-to-use/when-not statement and no named alternative for deferring publication, leaving the agent to match it against schedule_post on its own.

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.

Resources