Skip to main content
Glama
Sign In

Ignix

by social.ignix
OverviewDiscussionsAdmin

Hide or unhide a comment

moderate_comment
Destructive

Hide one comment from the public on a published post, or show it again with hidden: false. It is not deleted and it can be undone at any time. postId comes from list_comments and commentId from get_comment_thread. Supported on Facebook, Instagram, Threads, X and TikTok. It changes what the public sees: confirm with the user first.

Input Schema

NameRequiredDescriptionDefault
hiddenYestrue hides the comment, false shows it again.
postIdYesNetwork post id, from list_comments.
accountIdNoRestrict to one account (Ignix account id from list_accounts).
commentIdYesComment id, from get_comment_thread.
idempotencyKeyNoOptional. A unique id for this action (16-128 chars: letters, digits, _ : . -). If you are unsure whether a call went through (timeout, network error), repeat it with the SAME idempotencyKey and the same arguments: you get the original result and nothing is done twice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / commentId / description
      Added value: +"Comment id, from get_comment_thread."
    • changedInput schema / properties / hidden / description
      Previous value: -"true hides, false unhides."New value: +"true hides the comment, false shows it again."
    • changedInput schema / properties / postId / description
      Previous value: -"Network post the comment belongs to."New value: +"Network post id, from list_comments."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations: clarifies the comment is not deleted and the action is reversible at any time, notes it changes public visibility, and instructs confirming with the user first. This meaningfully softens and contextualizes destructiveHint=true, which would otherwise look riskier than it is.

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?

Four tight sentences, front-loaded with the core action, then reversibility, id provenance, platform support, and the confirmation guardrail. No filler.

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?

Covers what the tool does, both directions, reversibility, where ids come from, supported networks, and the confirmation requirement. With no output schema, this is sufficient for an agent to call it correctly and safely.

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 100%, so the schema already documents each parameter. The description's notes on `hidden` semantics and id sources largely repeat the schema rather than adding new format or constraint detail; baseline 3 applies.

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 the specific action (hide/show a comment) on a specific resource (a comment on a published post), and covers both directions via the `hidden` flag. Easily distinguished from siblings like reply_to_comment or set_booking_review_hidden, which operate on different resources.

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

Usage Guidelines4/5

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

Explains both modes (hide with true, unhide with false) inline and routes the agent to list_comments and get_comment_thread for the required ids. Adds a 'confirm with the user first' guardrail, but does not explicitly contrast with other comment-moderation siblings.

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

All Ignix toolsInspect
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