Skip to main content
Glama

Hide or show a comment

hide_comment
DestructiveIdempotent

Hides a comment from everyone but the account (hidden=true), or shows it again (hidden=false). Changes what the public sees: act on your human's request. Works on YouTube, Facebook Pages, Instagram and Threads only (list_comments can_hide); the account's own comments can't be hidden. X, LinkedIn, Bluesky and Mastodon offer no hiding to Shager: use delete_comment on the account's own replies instead. (Not available in an unclaimed sandbox.)

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>",
      "post_id": "<post_id>",
      "channel_id": "<channel_id>",
      "comment_id": "<comment_id>"
    },
    "name": "hide_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
hiddenNo
post_idYes
channel_idYes
comment_idYes
workspace_idYesWorkspace id from list_workspaces

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already give destructiveHint=true and idempotentHint=true, so the safety bar is met; the description adds real context beyond them — that the visibility change is public-facing, that it requires human authorization, the platform support matrix, the own-comment restriction, and the unclaimed-sandbox unavailability. No contradiction with the annotations (hiding is destructive because it changes public visibility).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and its flag semantics, then the authorization cue, then platform scope. Dense but every clause carries information; the parentheticals are compact rather than redundant. Slightly packed with platform lists, which costs a little readability.

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 destructive mutation with no output schema and five parameters, the description covers effect, authorization, platform eligibility and exclusions. What it omits is failure behavior (e.g. what happens if hiding is unsupported for that comment) and whether current hidden state is readable to decide the flag.

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 only 20% (only workspace_id documented), so the description must carry weight; it fully explains the `hidden` flag including its default direction (true = hide, false = show), which is the parameter most likely to be misused. However, post_id, channel_id and comment_id are left entirely to name inference, so the low-coverage gap is only partially closed.

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 pair and resource ('Hides a comment … or shows it again') and immediately defines the boolean semantics of both directions. It is clearly distinguishable from delete_comment, which is named as the different-mechanism alternative rather than a synonym.

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?

Explicit about when to use (act on your human's request), which platforms support hiding (YouTube, Facebook Pages, Instagram, Threads) and how to check (list_comments can_hide), which platforms do not (X, LinkedIn, Bluesky, Mastodon → delete_comment on own replies), and one exclusion ('the account's own comments can't be hidden'). Nothing is left 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