ig_hide_comment
Hide or show an Instagram comment by ID to moderate engagement on your posts.
Instructions
Hide or unhide an IG comment.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| hide | No | ||
| confirm | No | ||
| comment_id | Yes |
Hide or show an Instagram comment by ID to moderate engagement on your posts.
Hide or unhide an IG comment.
| Name | Required | Description | Default |
|---|---|---|---|
| hide | No | ||
| confirm | No | ||
| comment_id | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behavioral traits. It only mentions 'hide or unhide' and does not explain reversibility, permissions, side effects, or the role of the 'confirm' parameter. This is insufficient for a mutation tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single short sentence with no waste. It is front-loaded and efficient, though it sacrifices detail for brevity. Conciseness itself is good, but it borders on under-specification.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has 3 parameters, no annotations, and no output schema. The description fails to explain parameter semantics, return values, or when to use the tool. It is far from complete for an agent to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description does not mention any of the three parameters. The 'confirm' and 'hide' parameters are left completely unexplained, forcing the agent to guess their meaning. The description adds no value to parameter understanding.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action: hide or unhide an IG comment. It specifies the verb and resource, and distinguishes from sibling tools like ig_delete_comment (delete vs hide) and pages_hide_comment (Instagram vs Pages).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives. It does not mention that this is for Instagram comments only, nor does it point to pages_hide_comment for Facebook Pages. The usage context is only implied by the tool name and resource.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/AbnerZx/meta-ads-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server