Skip to main content
Glama

threads_channel_unhide_reply

Unhide a previously hidden reply on a Meta Threads post owned by the connected account. Also unhides its nested replies.

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

Input Schema

NameRequiredDescriptionDefault
reply_idYesThe Threads reply id to unhide.
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?

Annotations declare readOnlyHint=false and destructiveHint=false, so the description need not restate safety, and it instead adds genuinely new behavior: nested replies are also unhidden, and the post must be owned by the connected account. It does not say what happens when the reply was never hidden (despite idempotentHint=false), which is a remaining gap.

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 short sentences, both load-bearing: the first establishes action and target, the second discloses the cascade. Nothing is redundant or padded.

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 three-parameter mutation with no output schema, the description covers what changes and for whom, which is close to sufficient. It omits the result/error behavior and the no-op case, leaving the agent unsure how the call reports success.

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

Parameters4/5

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

Schema coverage is 100%, so reply_id, account_id, and in_workspace are already fully documented, and the account_id description even explains the omission rule. The description adds the scope note that nested replies are affected, which gently widens what the agent understands reply_id to reach. Baseline would be 3, but the cascade hint adds real meaning.

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?

States a concrete verb and resource ("Unhide a previously hidden reply on a Meta Threads post") plus ownership scope, and the second sentence clarifies the cascading effect on nested replies. It is clearly the inverse of the sibling hide-reply tool, though it never names that sibling explicitly.

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 implied by "previously hidden reply," which tells the agent the precondition, but there is no explicit when-to-use/when-not-to-use guidance and no named alternative tool. An agent can infer the context but must do so itself.

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.