Skip to main content
Glama

threads_channel_hide_reply

Hide a reply on a Meta Threads post owned by the connected account. Also hides every nested reply beneath it.

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_channel_hide_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
reply_idYesThe Threads reply id to hide.
account_idNoWhich connected Threads account to act as (id from channels.list). OMIT when the workspace has one; with several the call is refused and lists them.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / account_id
      Added value: +{
      +  "description": "Which connected Threads account to act as (id from channels.list). OMIT when the workspace has one; with several the call is refused and lists them.",
      +  "type": "integer"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  3. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), the description discloses the key hidden behavior: hiding cascades to every nested reply beneath the target. It also flags the ownership prerequisite. It does not discuss reversibility (though an unhide sibling implies it) or what happens on repeat calls, which matters given idempotentHint=false.

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, zero padding, with the cascade side effect front-loaded immediately after the core action. Every sentence earns its place.

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

Completeness4/5

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

For a three-parameter mutation with full schema coverage and annotations, the description supplies the two things structured fields cannot: the cascading deletion scope and the ownership prerequisite. Only edge-case behavior (already-hidden replies, error on non-owned posts) is left uncovered, which is a minor gap.

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 description coverage is 100%, so reply_id, account_id, and in_workspace are already fully documented in the schema, including the multi-account refusal rule. The description adds only the implicit notion of acting as the connected account, so the baseline 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 gives a specific verb and resource ('Hide a reply on a Meta Threads post') and scopes it to posts 'owned by the connected account', which cleanly separates it from the unhide sibling and from read-oriented siblings like threads_channel_list_posts. It stops short of naming an alternative tool explicitly, so it is clear rather than fully differentiating.

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 only implied: the ownership constraint tells the agent this is for replies on the account's own posts, but there is no statement of when to prefer this over other moderation tools, nor what to do if the reply is already hidden or not owned. The agent must infer the context.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.