Skip to main content
Glama

publish_post

Destructive

Returns a link the user opens to publish a draft themselves. Publishing is irreversible, and it goes out under the user's own name, so over MCP this tool does NOT publish: it returns a link the user opens to see the copy and the channels and press Publish themselves. Show them the link and wait. Do not try to confirm on their behalf. There is no argument that does that, and any you invent is ignored. (Over SMS/WhatsApp, where the user types publish 123 themselves, it publishes directly.) When the account has multiple connected accounts for a platform, pass platform_account_ids to target a specific one; the confirmation page names the account it will publish to.

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

Input Schema

NameRequiredDescriptionDefault
idYesPost id
platformsNoOptional. Defaults to the channels already selected on the draft. Instagram needs an image or video on the post: if it has none, add one with `update_draft` (`images`) first.
workspaceNoOptional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.
platform_account_idsNoOptional map of platform => connected_account_id (numeric id from `list_connected_accounts`). Example: {"linkedin": 42} to publish to the LinkedIn account with id 42. Each id must belong to the current account and match the platform.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspace
      Added value: +{
      +  "description": "Optional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

The description adds substantial context beyond the annotations: irreversibility, publishing under the user's own name, and the fact that over MCP the tool only returns a confirmation link rather than acting. This is consistent with destructiveHint=true and openWorldHint=true, but since the annotations already flag the operation as destructive and open-world, the marginal disclosure beyond them is more about workflow (do not act, wait for the user) than an additional destructive or side-effect property the agent could not already infer.

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?

It is front-loaded with the key fact (returns a link, does not publish) and the structure is logical. It is somewhat repetitive about the inability to force confirmation, repeating the same point twice, though that emphasis is defensible for a tool the agent might otherwise try to misuse.

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 four-parameter tool with no output schema, it explains the return value (a link), the channel-specific variant, and the account-targeting behavior. An agent has everything needed to call it correctly and to know not to attempt a direct publish.

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%, so the schema already documents id, platforms, workspace, and platform_account_ids in detail, including the Instagram media prerequisite. The description only repeats the platform_account_ids targeting rule and adds that the confirmation page names the account, so baseline 3 is appropriate; no syntax or format detail is added beyond the schema.

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?

The opening sentence names the exact resource and effect: it returns a link the user opens to publish a draft themselves. It also preempts the obvious misreading of the tool name by stating that over MCP it does NOT publish, which distinguishes it from siblings like approve_post, queue_post, and schedule_post.

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

Usage Guidelines5/5

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

It gives explicit operating instructions (show the link and wait, do not confirm on the user's behalf, no argument forces publication) and a channel-specific exception for SMS/WhatsApp where `publish 123` publishes directly. It also names the condition for using platform_account_ids: multiple connected accounts for a platform.

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