Skip to main content
Glama

Publish Text Thread

threads_publish_text

Publishes a text-only post to Threads. Creates a container and then publishes it, with optional reply, quote, location, or reply controls.

Instructions

Publishes a text-only post to Threads.

Two-step flow: creates a container, then publishes it.

Args:

  • threads_user_id (string): Threads user ID

  • text (string): Post text (up to 500 characters)

  • reply_to_id (string, optional): Thread ID to reply to

  • quote_post_id (string, optional): Thread ID to quote

Returns: Media ID of the published thread.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
threads_user_idYes
textYesPost text
reply_to_idNoThread ID to reply to
quote_post_idNoThread ID to quote
reply_controlNoWho can reply to this post
location_idNoLocation ID to tag (from Facebook Places search)
response_formatNoOutput format: 'markdown' for human-readable or 'json' for machine-readablemarkdown
Behavior3/5

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

Annotations provide little info (readOnlyHint=false, destructiveHint=false), so the description should disclose more. It mentions the two-step flow and returns a media ID, but lacks details on side effects, rate limits, or authentication needs.

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 concise: 3 sentences plus a parameter list. It front-loads the purpose and includes the two-step flow. However, the parameter list is somewhat redundant with the schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description mentions the return value (media ID). However, it does not explain the two-step flow in detail, and omits optional parameters. It is adequate but not comprehensive.

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

Parameters2/5

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

Schema coverage is 86%, but the description lists only 4 of 7 parameters, omitting reply_control, location_id, and response_format. The description adds minimal value beyond the schema, and missing parameters reduce completeness.

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 clearly states it publishes a text-only post to Threads, distinguishing it from siblings like threads_publish_image or threads_publish_video by specifying 'text-only'. It also mentions the two-step flow.

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

Usage Guidelines2/5

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

The description does not provide guidance on when to use this tool versus alternatives (e.g., other publish tools). It mentions a two-step flow but no context on prerequisites or when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/oliverames/meta-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server