Rizamo

Hide a comment

hide_comment

DestructiveIdempotent

Use this to hide a comment on its network as the account, such as spam or abuse, or to show it again with hidden false: others stop seeing it, and the person who wrote it may not notice. Not for the account's own comments: delete those. Instagram, Facebook, TikTok and Threads hide comments from others; YouTube's are hidden in YouTube Studio, not here. Threads hides only first-level replies, with the replies under them; Instagram nothing on live videos. It leaves the thread open: close it with update_thread.

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": {
      "id": "<id>",
      "messageId": "<messageId>",
      "hidden": "<hidden>"
    },
    "name": "hide_comment"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	The thread's id (`thr_`).
`hidden`	Yes	True hides it, false shows it again.
`messageId`	Yes	The comment's message id (`msg_`), from Get a thread.
`idempotencyKey`	No	Optional. A new unique string for each new action, such as a UUID. When a call timed out or failed and you send it again, send the same key: for 24 hours the same call gets the first one's answer instead of doing it twice.

Output Schema

Name	Required	Description	Default
`at`	No
`id`	No
`text`	No
`first`	No
`liked`	No
`author`	No
`hidden`	No
`sentBy`	No
`delivery`	No
`threadId`	No
`direction`	No
`deliveryError`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, but the description adds genuinely non-obvious effects: others stop seeing the comment, the author may not notice, and the thread is left open. The remaining gap is that it doesn't restate reversibility/retry behavior beyond the schema's idempotencyKey field, though the hide/show pair implicitly covers reversibility.

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?

Purpose and the primary exclusion are front-loaded, and every sentence carries platform-specific information rather than filler. It is dense and slightly run-on in the caveat cluster, but nothing is redundant with the annotations or schema in a wasteful way.

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

Completeness5/5

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

With an output schema present, annotations covering safety and idempotency, and full schema coverage on all four parameters, the description supplies exactly the missing layer: cross-platform behavior differences and sibling routing. Nothing an agent needs in order to call this correctly is absent.

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 the baseline is 3; the description's 'hidden false' phrasing restates what the hidden boolean already documents. It adds only the framing that the action is performed 'as the account', no syntax or format detail beyond the schema.

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?

The first clause gives a specific verb+resource ('hide a comment on its network') plus the inverse operation ('show it again with hidden false'), and it explicitly carves out what it is not: 'Not for the account's own comments: delete those.' An agent can distinguish it from delete_comment and update_thread without opening either 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?

It names alternatives and the exact condition that selects them: own comments go to delete_comment, and closing the thread goes to update_thread. It also spells out platform-level when-not cases (YouTube hidden in Studio, Threads only first-level replies, Instagram nothing on live videos), which is real routing guidance rather than implied usage.

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

All Rizamo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?