Skip to main content
Glama

hide_comment

Idempotent

Hide a comment so only its author (and the account) can see it — or, with hidden=false, show it again. Nothing is deleted and the author is not told, so it is the safe first step for spam or abuse; prefer it to delete_comment unless the user asked to remove the comment.

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": {
      "workspace_id": "<workspace_id>",
      "ig_account_id": "<ig_account_id>",
      "comment_id": "<comment_id>"
    },
    "name": "hide_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
hiddenNo
comment_idYes
workspace_idYes
ig_account_idYes

Output Schema

NameRequiredDescriptionDefault
statusYes
reply_idNo
comment_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=false and idempotentHint=true, so the safety profile is partly given; the description adds the mechanism behind it — nothing is deleted, the author is not notified, and the change is reversible with hidden=false. That is real context beyond structured fields, though it does not cover auth/permission requirements or what the response contains.

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, front-loaded with the effect first, then reversibility and the routing decision. No filler, no repetition of the tool name or schema fields.

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?

An output schema exists, so return values need not be described, and the annotations plus the description together cover safety, reversibility and alternatives for a simple 4-parameter toggle. The only shortfall is the absence of any per-parameter description for the three required IDs under 0% schema coverage.

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 coverage is 0%, so the description must carry parameter meaning; it explains the one non-obvious parameter (hidden=false restores visibility) but says nothing about workspace_id, ig_account_id or comment_id. Those three are self-describing identifiers, so the omission is tolerable but not fully compensating for the coverage gap.

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?

States a specific verb and resource ('Hide a comment') plus the exact resulting visibility rule (only its author and the account can see it), and covers the inverse operation via hidden=false. An agent can distinguish this from delete_comment or reply_to_comment without opening any schema.

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

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use guidance ('the safe first step for spam or abuse') and names the alternative with the selecting condition ('prefer it to delete_comment unless the user asked to remove the comment'). Both the preferred path and the exclusion are stated, leaving nothing to inference.

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.

Resources