Instagram MCP Server

delete_comment

Permanently remove a specific Instagram comment by its ID. Use for spam, abuse, or content violating community standards, as this action cannot be undone.

Instructions

Permanently delete a comment.

THIS IS A WRITE/DESTRUCTIVE OPERATION. Cannot be undone. Prefer hide_comment unless the comment is clearly spam, abuse, or violating your community standards.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`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.7/5.0

Behavior5/5

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

No annotations provided; description fully discloses destructive nature: 'THIS IS A WRITE/DESTRUCTIVE OPERATION. Cannot be undone.' This is critical for agent decision-making.

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 sentences, no wasted words. Critical behavioral warning front-loaded. Each sentence serves a purpose.

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?

Tool has one parameter and output schema exists. Description covers purpose, destructiveness, usage guidance, and sibling differentiation. Complete for a delete action.

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 'Comment ID from get_comments' for the only parameter. Description adds little beyond schema, but the context of permanence implies the comment must exist. Baseline 3 is appropriate.

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 'Permanently delete a comment' with strong verb and resource. It distinguishes from hide_comment by specifying the appropriate use case.

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 advises to prefer hide_comment unless the comment is spam, abuse, or violating standards. Provides clear when-to-use and when-not-to-use guidance.

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