Skip to main content
Glama
exileum

meta-mcp

threads_publish_video

Publish a video post on Threads with captions, alt text, topic tags, quote posts, spoiler marking, geo-gating, and location tagging. Waits for video processing and supports cross-share to Instagram Stories.

Instructions

Publish a video post on Threads. Waits for video processing. 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. Note: cross-share to IG Stories may silently fail for video posts (the Threads post still publishes).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textNoCaption text
alt_textNoAlt text for accessibility (max 1000 chars)
topic_tagNoTopic tag for the post (1-50 chars, no periods or ampersands)
video_urlYesPublic HTTPS URL of the video (MP4/MOV, max 1GB, up to 5 min)
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?

The description goes beyond annotations by revealing two key behavioral traits: it 'waits for video processing' and that 'cross-share to IG Stories may silently fail'. This adds meaningful context about the tool's runtime behavior and potential partial failures.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise (4 sentences) and front-loaded with the primary action. Every sentence serves a purpose: stating the action, noting the wait behavior, listing features, and warning about a potential silent failure.

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 the tool has no output schema, the description omits information about return values (e.g., post ID or container status) and does not discuss rate limits or authentication beyond what is in the schema. While it covers usage context, it lacks outcome details.

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?

The input schema already provides detailed descriptions for all 10 parameters (100% coverage). The tool description offers a high-level summary of features but does not add significant semantic value beyond what the schema already documents.

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 'Publish a video post on Threads', specifying the verb (publish) and resource (video post). It distinguishes this tool from sibling publish tools (e.g., threads_publish_image, threads_publish_text) by explicitly focusing on video posts.

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 supported features (topic tag, quote post, alt text, etc.) but does not provide explicit guidance on when to use this tool versus alternatives like threads_publish_carousel or threads_publish_image. It implies usage when a video URL is available, but no exclusion criteria or prerequisites are stated.

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