Skip to main content
Glama

Publish or schedule a post

publish
Destructive

Publishes a post to Threads now (publish_now:true) or at publish_at (ISO 8601 with offset). Takes text, one public https image (media_urls with 1 url), a carousel (2 to 10 urls) or a video_url. Text over 500 characters is split into a thread. Publishing now or within 30 minutes uses the publish-now permission; a post 30 minutes or more ahead uses the schedule permission. Either may wait for the owner's confirmation when that permission is set to ask on this connection. publish_at takes any offset and comes back in UTC (Z); a publish_at more than 60 seconds in the past returns 400 publish_at_in_past with server_now. The same account needs at least 10 minutes between scheduled posts: a closer publish_at returns 400 schedule_too_dense with nearest_publish_at. idempotency_key makes a retried request return the first result instead of posting twice. Applies when the user has final text and wants it on Threads.

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": {
      "account_id": "<account_id>"
    },
    "name": "publish"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoPost text / caption
video_urlNoPublic https MP4/MOV
account_idYesAccount id
media_urlsNoPublic https image URLs (1 = image, 2-10 = carousel)
publish_atNoISO 8601 if not publish_now
publish_nowNoPublish immediately
idempotency_keyNoOptional

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations: names the permission model (publish-now vs schedule), the owner-confirmation hold, the 10-minute spacing rule, the 60-second past-window, and the exact 400 error codes and payload fields returned. Idempotency key semantics are spelled out, which usefully explains why idempotentHint is false while retries are still safe.

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?

Front-loaded with the core now-vs-scheduled decision, then progressively adds media, permissions, and error detail. Dense but nearly every sentence carries operational information; the single unbroken paragraph makes it slightly harder to scan than a short bulleted structure would.

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 seven parameters and no output schema, it covers modes, media constraints, permissions, spacing rules, and failure modes thoroughly. The one gap is the success response shape (post id, scheduled status), which the agent must discover empirically.

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

Parameters5/5

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

Despite 100% schema coverage, the description adds real meaning: media_urls cardinality maps to image vs carousel (1 vs 2-10), publish_at accepts any offset and normalizes to UTC Z, text over 500 characters is auto-split into a thread, and idempotency_key changes retry behavior. This is meaning the schema's one-line field descriptions do not convey.

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 (publishes a post to Threads) and immediately splits the two modes: now via publish_now:true or later via publish_at. An agent can tell exactly what this does without opening the schema.

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 closing sentence gives a clear activation condition (user has final text and wants it on Threads), and the publish_now/publish_at rules imply the scheduling path. It does not, however, explicitly route to siblings like schedule_text or cancel_schedule, so the agent must infer which tool owns a pure scheduling request.

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.