instagram-mcp

delete_comment

Permanently delete a comment you own or on your media using its comment ID. This action is irreversible.

Instructions

Permanently delete a comment you own (or a comment on your media). Irreversible.

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": "delete_comment"
  }
}

Input Schema

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

A3.9/5.0

Behavior4/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It clearly flags that the action is irreversible and restricts deletion to owned comments or comments on the user's media, which are the critical operational traits. It does not discuss account or auth requirements, but the highest-risk behavior is disclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single front-loaded sentence with no filler or unnecessary detail. It is slightly redundant with 'Permanently' and 'Irreversible' conveying the same idea, but this does not meaningfully hurt readability.

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?

The core destructive semantics and scope are present, and the output schema covers return values, but the optional account parameter is not explained and there is no guidance for multi-account contexts. The tool is usable with just comment_id, but the definition is not fully self-sufficient.

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%, and the description mentions neither comment_id nor the optional account parameter. The parameter names are somewhat self-explanatory, but the description adds no meaning beyond the schema and leaves the nullable/default account behavior unexplained.

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 states a specific verb and resource ('Permanently delete a comment') and adds the ownership/media scope, making the operation unambiguous. It also clearly distinguishes this from the sibling hide_comment by emphasizing permanence and irreversibility.

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?

It gives an explicit condition for use: 'a comment you own (or a comment on your media)'. This helps an agent determine when deletion is appropriate, but it does not name alternatives like hide_comment or state when not to use this tool.

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