threads-mcp

post_carousel

Create carousel posts on Threads by combining multiple images and videos with optional text.

Instructions

Dang carousel (nhieu anh/video) len Threads.

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": {
      "items": "<items>"
    },
    "name": "post_carousel"
  }
}

Input Schema

Name	Required	Description	Default
`text`	No
`items`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 28, 2026

TDQS

C2/5.0

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'post carousel' which implies a write operation, but does not reveal constraints (e.g., limits on items, mixing images/videos, permission requirements, or what happens on success). This is insufficient for safe invocation.

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

Conciseness2/5

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

The description is very concise (one short sentence), but it is in Vietnamese, which may hinder English-only agents. It lacks structure and front-loading of key information. Conciseness is undermined by poor clarity.

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

Completeness1/5

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

Given the tool's complexity (nested items array, optional text, multiple siblings), the description is grossly incomplete. No output schema, no examples, no prerequisites or limits. It fails to provide enough context for correct use.

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

Parameters1/5

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

Schema coverage is 0%, and the description adds no information about the 'text' or 'items' parameters. The agent must rely solely on the schema, which lacks descriptions. The description provides zero value for parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The Vietnamese description 'Dang carousel (nhieu anh/video) len Threads' indicates posting a carousel (multiple photos/videos) to Threads, which conveys the basic action and resource. However, it does not differentiate from sibling tools like post_image or post_video, and the term 'carousel' is not explained. A score of 3 reflects adequate but not clear purpose.

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?

No guidance on when to use this tool versus alternatives. The description does not mention when to prefer a carousel over multiple single-media posts or other siblings. The lack of usage context makes it hard for an agent to decide.

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

Deploy Server