Skip to main content
Glama
exileum

meta-mcp

threads_publish_image

Publish image posts on Threads with caption, alt text, topic tags, quote posts, spoiler flags, location tagging, reply controls, cross-sharing to Instagram Stories, and geo-gating by country codes.

Instructions

Publish an image post on Threads. Supports topic tag, quote post, alt text, spoiler flag, cross-share to Instagram Stories, geo-gating via allowlisted_country_codes, and location tagging via location_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoCaption text
alt_textNoAlt text for accessibility (max 1000 chars)
image_urlYesPublic HTTPS URL of the image (JPEG/PNG, max 8MB)
topic_tagNoTopic tag for the post (1-50 chars, no periods or ampersands)
is_spoilerNoMark content as spoiler
location_idNoLocation ID for tagging the post. Use threads_search_locations to find IDs. Requires the threads_location_tagging permission on the access token.
quote_post_idNoID of a post to quote
reply_controlNoWho can reply to this post. One of: 'everyone' (default — anyone can reply), 'accounts_you_follow' (only profiles the author follows), 'mentioned_only' (only profiles @-mentioned in the post), 'parent_post_author_only' (only the author of the post being replied to — applies when this post is itself a reply, not a quote), or 'followers_only' (only the author's followers). See https://developers.facebook.com/docs/threads/reply-management/ for the authoritative list.
share_to_ig_storyNoCross-share this post to linked Instagram as a Story. 'light' = normal, 'dark' = dark mode. Requires threads_share_to_instagram permission and a linked Instagram account. The Threads post still publishes even if cross-share fails.
allowlisted_country_codesNoISO 3166-1 alpha-2 country codes (e.g., ['US','CA','GB']) restricting post visibility to those countries (geo-gating). Requires the account to be eligible — check `is_eligible_for_geo_gating` via `threads_get_profile`. The creator can always see their own posts regardless. Codes are normalized to uppercase and sent comma-joined (e.g., 'US,CA') as required by the API.
Behavior4/5

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

Annotations indicate mutation (readOnlyHint=false), and the description adds behavioral details: cross-share failure handling ('post still publishes'), geo-gating creator visibility, and permission requirements (e.g., threads_location_tagging, threads_share_to_instagram). No contradictions with annotations.

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 a single sentence listing features—concise but lacking structural breaks. The main purpose is front-loaded, and every element earns its place.

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?

With 10 parameters, 1 required, and no output schema, the description covers all major features and their nuances (e.g., cross-share failure, geo-gating eligibility). Slightly better than adequate, but could include a usage example or return value hint.

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 coverage is 100%, but the description significantly enhances understanding: explains how to find location IDs, elaborates reply_control options, normalizes country codes, and clarifies cross-share behavior. This adds value beyond the schema.

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 explicitly states the tool's purpose: 'Publish an image post on Threads.' It lists supported features (topic tag, quote post, alt text, spoiler flag, cross-share, geo-gating, location tagging), clearly distinguishing it from siblings like threads_publish_text and threads_publish_carousel.

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?

The description lists features specific to image posts but does not explicitly state when to use this tool over alternatives. There are no exclusions or conditional guidance, leaving the agent to infer purpose from the listed features.

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/exileum/meta-mcp'

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