Skip to main content
Glama
Sign In
Enterprise Threads MCP Server

Enterprise Threads MCP Server

by baguskto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

repost_thread

Share a thread on Threads by reposting it with just its post ID.

Instructions

Repost/share another thread

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": {
      "post_id": "<post_id>"
    },
    "name": "repost_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
post_idYesID of the post to repost

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv5.1.0

TDQS

C2.6/5.0
Behavior1/5

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

No annotations are present, and the description is a near-verbatim restatement of the tool name. It does not disclose side effects, permission requirements, or the impact on the original thread or the user's profile, providing no behavioral context beyond the verb.

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

Conciseness3/5

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

The description is a single short sentence with no wasted words, but it is so minimal that it fails to provide context, making it under-specified rather than effectively concise. It does not front-load any additional useful detail.

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

Completeness2/5

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

For a mutation tool with no output schema, the description should explain that a repost is created, its visibility, or how to undo it using unrepost_thread. It does none of this, leaving the agent to infer behavior and lacking completeness for even a simple tool.

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 schema already fully documents the single parameter post_id with its description 'ID of the post to repost', achieving 100% schema coverage. The description adds no parametric information, so the baseline score of 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?

The description uses the verb 'repost/share' with the resource 'another thread', clearly indicating the action. However, it does not explicitly distinguish this from similar tools like quote_post or publish_thread, so it lacks sibling differentiation.

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 is provided on when to use repost_thread versus alternatives such as quote_post or publish_thread. There are no stated prerequisites, conditions, or exclusions, leaving the agent without context for tool selection.

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

Deploy Server

Other Tools