Skip to main content
Glama

Social0

publish_now

Destructive

Create content and publish it live to connected platforms in one step (writes to external social networks). Prefer this over create_draft when the user wants to post immediately.

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": {
      "content": "<content>",
      "platforms": "<platforms>"
    },
    "name": "publish_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
mediaNoMedia IDs from upload_media
contentYesPost caption
platformsYesTarget platforms or account IDs
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

A4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=false, destructiveHint=true, openWorldHint=true, and idempotentHint=false, so an agent already knows this is a non-idempotent, externally visible write. The description adds value by explaining the combined create-and-publish flow and by clarifying that the content goes live immediately to external social networks in one step. It does not warn that publishing is irreversible or that connected accounts or permissions are needed, which leaves a modest gap.

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?

Two sentences, both necessary: the first states the action and its external side effect, and the second states the routing rule for choosing this tool over an alternative. The action and side effect appear before the alternative, and nothing is redundant.

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, externally visible write tool, the important elements are present: what it creates, that it publishes live, that it affects external networks, and when to choose it over drafting. Annotations and the rich, fully described schema cover permissions flags and per-platform settings. Minor gaps remain around irreversibility and why this tool differs from publish_post, but they do not undermine correct invocation.

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 description coverage is 100%, including detailed per-platform options in platform_options, so the schema already carries nearly all parameter semantics. The description does not explain the required content/platforms pairing or how media IDs relate to upload_media. When the schema already does the heavy lifting, this silent description meets the baseline rather than adding more.

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?

The description names a specific verb and resource: it creates content and publishes it live to connected platforms in a single step. It also distinguishes this tool from one close sibling by saying it is preferred over create_draft. It does not address publish_post or schedule_content, which also appear in the sibling list and may overlap in purpose, so the tool is not completely unambiguous amid all siblings.

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?

The description gives explicit selection guidance: 'Prefer this over create_draft when the user wants to post immediately.' It therefore names an alternative tool and the condition that selects it. It does not say when this tool should not be used, and it does not mention other possibly overlapping siblings such as publish_post or schedule_content, but the given guidance is clear and actionable.

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.