meta-mcp

threads_publish_image

Publish an image post to Threads with caption, alt text, topic tag, quote post, spoiler flag, reply controls, and optional Instagram Story cross-sharing.

Instructions

Publish an image post on Threads. Supports topic tag, quote post, alt text, and spoiler flag.

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": {
      "image_url": "<image_url>"
    },
    "name": "threads_publish_image"
  }
}

Input Schema

Name	Required	Description
`text`	No	Caption text
`alt_text`	No	Alt text for accessibility (max 1000 chars)
`image_url`	Yes	Public HTTPS URL of the image (JPEG/PNG, max 8MB)
`topic_tag`	No	Topic tag for the post
`is_spoiler`	No	Mark content as spoiler
`location_id`	No	Location ID to tag (from threads_search_locations)
`quote_post_id`	No	ID of a post to quote
`reply_control`	No	Who can reply
`crossreshare_to_ig`	No	Also share this post to the user's linked Instagram account as a Story
`enable_reply_approvals`	No	Require replies to be approved before they're published
`crossreshare_to_ig_dark_mode`	No	Cross-share to Instagram Stories in dark mode

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.2.2Oct 26, 2026

addedInput schema / properties / crossreshare_to_ig

Added value: +{
+  "description": "Also share this post to the user's linked Instagram account as a Story",
+  "type": "boolean"
+}

addedInput schema / properties / crossreshare_to_ig_dark_mode

Added value: +{
+  "description": "Cross-share to Instagram Stories in dark mode",
+  "type": "boolean"
+}

addedInput schema / properties / enable_reply_approvals

Added value: +{
+  "description": "Require replies to be approved before they're published",
+  "type": "boolean"
+}

addedInput schema / properties / location_id

Added value: +{
+  "description": "Location ID to tag (from threads_search_locations)",
+  "type": "string"
+}

First observedv2.0.1Mar 19, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: it does not say the call is an irreversible public write, whether it requires a token/permission set, whether publishing limits apply (threads_get_publishing_limit exists as a sibling), or whether a container must be polled via threads_get_container_status first.

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?

Two short sentences with the core action front-loaded and a compact capability summary after it. Nothing is padded, though the capability list is largely redundant with the schema.

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 an 11-parameter mutation with no annotations and no output schema, the description leaves meaningful gaps: it never says what a successful call returns (post ID vs. container ID) or whether the two-step container/publish flow applies, which the presence of threads_get_container_status strongly implies. The 100% schema coverage offsets the parameter detail gaps, but the return/async story is absent.

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%, so the schema already documents all 11 parameters including formats, max lengths, and the reply_control enum. The description's mention of topic tag, quote post, alt text, and spoiler flag merely echoes a subset of the schema and adds no format or behavioral detail beyond it, so baseline 3 applies.

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?

States a specific verb and resource ("Publish an image post on Threads"), which separates it from threads_publish_text, threads_publish_video, and threads_publish_carousel among the siblings. It stops short of naming those alternatives, so it is clear but not fully differentiated.

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?

Usage is only implied by the tool name and the phrase "image post". There is no explicit statement of when to choose this over threads_publish_carousel (multiple images) or threads_publish_text, and no note on prerequisites such as a reachable image URL or the linked-account requirement for crossreshare.

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

Deploy Server