Skip to main content
Glama
Sign In
threads-mcp

threads-mcp

by Maz1n0-zzz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_replies

Retrieve all replies to a specific thread by providing its ID, enabling review of responses to a post.

Instructions

Lay cac reply cua mot bai.

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": {
      "thread_id": "<thread_id>"
    },
    "name": "get_replies"
  }
}

Input Schema

NameRequiredDescriptionDefault
thread_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

D1.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 does not disclose behavioral traits such as whether results are ordered, paginated, or include nested replies. The agent is left guessing about side effects or limitations.

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 extremely brief (one short sentence), but it sacrifices necessary information for brevity. It is not appropriately sized for the tool's complexity and lacks front-loaded structure.

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 lack of annotations, output schema, and minimal description, the tool is under-specified. It does not address return values, error behavior, or scope (e.g., all replies or only top-level).

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?

The input schema has 1 required parameter (thread_id) with 0% schema description coverage. The description does not explain what thread_id represents or its expected format, leaving the agent without context beyond the schema's type.

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 description 'Get the replies of a post' (translated from Vietnamese) clearly states the action and resource, but the use of a non-English language may hinder an AI agent's understanding, lowering clarity. It does distinguish from siblings like 'get_thread' or 'reply'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/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 this tool versus alternatives such as 'get_thread' or 'reply'. There is no mention of prerequisites or context.

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