instagram-mcp

hide_comment

Hide or unhide an Instagram comment from public view. Use the hide parameter; set hide=false to make a hidden comment visible again.

Instructions

Hide (or unhide) a comment from public view. hide=false unhides.

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

Input Schema

Name	Required	Description	Default
`hide`	No
`account`	No
`comment_id`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.2Jul 29, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It usefully states that the operation is reversible ('hide=false unhides') and scoped to 'public view', which implies the comment is not deleted. However, it omits any mention of permissions, account context, or side effects, so coverage is adequate but not rich.

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?

Two short sentences, no filler, and the most important behavioral detail ('hide=false unhides') is front-loaded. Every word earns its place.

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

Completeness3/5

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

For a simple toggle tool with an output schema, the description is minimally workable but leaves gaps: there is no usage guidance and no explanation of the optional 'account' parameter. The agent can probably call it correctly using the schema, but the definition is not fully self-contained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate for all three parameters. It explains the 'hide' parameter's false behavior, and 'comment_id' is inferable from its name, but the 'account' parameter is entirely unexplained and could be ambiguous.

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 description uses a specific verb ('Hide') and resource ('a comment'), and clearly indicates it toggles visibility with 'hide=false unhides'. The phrase 'from public view' differentiates this from permanent deletion, which is a key sibling alternative.

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

Usage Guidelines2/5

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

No guidance is provided about when to use this tool versus alternatives like delete_comment or reply_to_comment. The description states the action but does not offer exclusions, prerequisites, or routing to a sibling tool.

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