insta-pilot

ig_comment_delete

Destructive

Permanently deletes an Instagram comment by comment_id through the official API, with a dry_run preview before irreversible removal.

Instructions

Elimina un comentario (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": "ig_comment_delete"
  }
}

Input Schema

Name	Required	Description
`account`	No	Usuario de Instagram configurado (por defecto la cuenta activa)
`dry_run`	No	true = solo muestra lo que haría, sin ejecutar
`comment_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Oct 20, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is largely covered. The description adds the useful explicit qualifier '(irreversible)', reinforcing permanence, but omits auth requirements, the effect of dry_run, or whether removal is soft/hard beyond that.

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?

A single front-loaded sentence with zero filler; the destructive warning is stated immediately. Nothing is wasted, though the economy borders on under-specification.

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 destructive operation with annotations covering the safety profile and no output schema to explain, the essential warning is present. However, it omits the routing distinction from sibling comment tools and any note on the undocumented required comment_id.

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 coverage is 67%: account and dry_run are described, but the required comment_id carries no schema description. The tool description adds no parameter information to compensate for that gap, leaving the most critical argument underspecified.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Elimina un comentario') that an agent can immediately map to a delete operation. It does not, however, distinguish this from sibling comment tools such as ig_comment_hide, ig_comments_toggle, or ig_comments, which an agent must route between.

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?

The description gives no guidance on when to delete versus hide or toggle a comment, nor any preconditions (e.g., ownership or permissions). The agent must infer the distinction from sibling names alone.

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