Instagram MCP Server

hide_comment

Hide or unhide Instagram comments to make them invisible to others without deletion, ideal for managing spam or troll comments.

Instructions

Hide or unhide a comment. Hidden comments are invisible to others but not deleted.

THIS IS A WRITE OPERATION. Useful for spam/troll comments you'd rather not fully delete.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`hide`	No	True to hide, False to unhide
`comment_id`	Yes	Comment ID from get_comments

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 16, 2026

TDQS

A4.5/5.0

Behavior4/5

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

No annotations provided, but description adds behavioral context: it's a write operation, comments become invisible but not deleted, and the action is reversible. Could include permissions or rate limits but is adequate.

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?

Extremely concise with two front-loaded sentences, each providing essential information without waste.

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, the description sufficiently covers purpose, behavior, and use case for a simple tool with two parameters.

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% with clear parameter descriptions; the description does not add additional meaning beyond the schema, meeting the baseline.

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?

Description clearly states the verb (hide/unhide) and resource (comment), and distinguishes from deletion by noting that hidden comments are invisible but not deleted.

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?

Explicitly states usefulness for spam/troll comments as an alternative to full deletion, providing clear when-to-use guidance.

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