Skip to main content
Glama
Sign In
meta-mcp

meta-mcp

by mikusnuz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

threads_hide_reply

Hide a reply on your Threads post to moderate the visible conversation. Hidden replies stay accessible if someone has the direct link.

Instructions

Hide a reply on your Threads post. Hidden replies are still visible if directly accessed.

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": {
      "reply_id": "<reply_id>"
    },
    "name": "threads_hide_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
reply_idYesReply ID to hide

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.1

TDQS

A3.7/5.0
Behavior3/5

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

No annotations provided. Description adds one behavioral trait: 'Hidden replies are still visible if directly accessed.' This is useful but lacks details on permissions, reversibility, or side effects. Adequate for a simple action.

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?

Two sentences, no redundant words. Front-loaded with the action: 'Hide a reply on your Threads post.' Every word adds value.

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 a simple tool with one parameter and no output schema, the description is minimally complete. However, it lacks context like prerequisites (e.g., post ownership) or confirmation that the operation is reversible via sibling tool. Could be considered adequate but not rich.

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 has 100% coverage with description for reply_id. Description does not add any extra meaning beyond the schema. Baseline score 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?

Description clearly states verb 'hide' and resource 'reply on your Threads post', making purpose unambiguous. It distinguishes from siblings like 'threads_unhide_reply' and 'ig_hide_comment' by specifying 'Threads'.

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?

No explicit guidance on when to use this tool vs alternatives. The sibling 'threads_unhide_reply' implies the reverse operation, but description does not mention when to use (e.g., only for own posts) or when not to use.

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