meta-mcp

threads_publish_video

Publish a video post to Threads and wait for processing, with caption, topic tag, quote post, alt text, and spoiler options.

Instructions

Publish a video post on Threads. Waits for video processing. 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": {
      "video_url": "<video_url>"
    },
    "name": "threads_publish_video"
  }
}

Input Schema

Name	Required	Description
`text`	No	Caption text
`alt_text`	No	Alt text for accessibility (max 1000 chars)
`topic_tag`	No	Topic tag for the post
`video_url`	Yes	Public HTTPS URL of the video (MP4/MOV, max 1GB, up to 5 min)
`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

A3.7/5.0

Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the call 'waits for video processing,' which tells the agent this is a blocking/long-running operation. It does not cover auth requirements, rate limits, what is returned (e.g., post ID), or what happens if processing fails.

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?

Three short sentences, front-loaded with the action and resource. The blocking behavior is placed early, and no sentence is wasted.

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?

For an 11-parameter publish tool with no annotations and no output schema, the description should say more about the outcome—what is returned and how failures/timeouts during video processing are surfaced. The 'waits for video processing' note is helpful but leaves the response contract unspecified.

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 coverage is 100%, so every parameter is already documented in the input schema with constraints and descriptions. The description lists four supported features (topic tag, quote post, alt text, spoiler flag) but adds no semantics beyond what the schema provides, so the baseline of 3 applies.

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?

States a specific verb and resource: 'Publish a video post on Threads.' The word 'video' cleanly separates it from siblings like threads_publish_text, threads_publish_image, and threads_publish_carousel without needing to name them.

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 implied by the resource type: use this for video posts, not text/image/carousel. However, there is no explicit guidance on when to prefer ig_publish_video vs threads_publish_video, or when the caller should check threads_get_container_status before calling.

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

Deploy Server