Skip to main content
Glama
Threads MCP

Threads MCP

by kerwilgil

Publish Threads text

threads_publish_text
Idempotent

Publish an approved text post to Threads with a stable idempotency key to prevent duplicate retries and avoid blind retries when the provider outcome is unknown.

Instructions

Publish one approved text post to Threads. idempotency_key must remain stable for retries of the same logical publication. Optional topic_tag (1-50 characters without '.' or '&'). Optional image_url (public HTTPS) turns the call into an image post, exactly like threads_publish_image. The tool prevents blind retries when provider outcome is unknown.

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": {
      "text": "<text>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "threads_publish_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
image_urlNo
topic_tagNo
idempotency_keyYes

Output Schema

NameRequiredDescriptionDefault
statusYes
messageNo
post_idNo
permalinkNo
recoveredNo
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare idempotentHint=true, openWorldHint=true, and destructiveHint=false. The description adds valuable behavioral context beyond those hints: the idempotency key must remain stable for retries of the same logical publication, and the tool prevents blind retries when provider outcome is unknown. It still does not discuss permissions, rate limits, or approval workflow details.

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?

The description is front-loaded with the core action and then covers key retry and parameter behavior in compact sentences. The final sentence is slightly vague but still earns its place by explaining retry safety. Overall it is concise with little unnecessary wording.

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 publishing tool with an output schema and annotations covering safety and idempotency, the description provides enough detail to call it correctly. It documents the important retry semantics and the parameter behaviors. Remaining gaps such as approval workflow and auth details are less critical given the surrounding structured data.

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 description coverage is 0%, so the description must carry parameter meaning. It explains idempotency_key stability for retries, topic_tag length and character restrictions, and image_url as a public HTTPS URL that changes the call into an image post. Only text lacks additional constraints or content guidance.

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 description states a specific verb and resource: publish one approved text post to Threads. It also distinguishes the tool from threads_publish_image by explaining that adding image_url turns the call into an image post exactly like that sibling. An agent can identify the core operation 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 Guidelines3/5

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

It implies usage via 'one approved text post' and notes the overlap with threads_publish_image when image_url is supplied. However, it does not explicitly say when to prefer this tool over threads_publish_image, nor does it state when not to use it. The guidance is useful but leaves the alternative-selection decision implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.