Skip to main content
Glama
Sign In
instagram-mcp-server

instagram-mcp-server

by qaassimq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Delete Comment

instagram_delete_comment
DestructiveIdempotent

Permanently deletes an Instagram comment authored by the account or posted on its own media. This action cannot be undone; use hide for reversible moderation.

Instructions

Permanently delete a comment.

Works on comments the account authored, and on comments by others on the account's own media. This cannot be undone — instagram_hide_comment is the reversible alternative.

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

Input Schema

NameRequiredDescriptionDefault
comment_idYesComment ID to delete permanently

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered structurally. The description adds real value beyond them by stating the permanence explicitly and, more importantly, disclosing the authority boundary on which comments are deletable. It does not say what happens on an unknown or already-deleted comment_id, which would complete the picture.

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?

Three short sentences, each doing distinct work: action, scope, and alternative. Irreversibility is front-loaded before the scope caveat, so the most decision-relevant fact lands first with zero filler.

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

Completeness4/5

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

For a one-parameter destructive tool with full annotations and no output schema, the description covers the essentials: what it does, what it destroys, and the reversible option. Minor gap: no note on error behavior for invalid or already-removed comments, which matters for a destructive operation.

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?

There is a single parameter with 100% schema description coverage, so the schema already explains comment_id. The description adds no format, source, or lookup guidance for obtaining a valid ID, so it sits at the baseline for a fully-documented schema.

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?

"Permanently delete a comment" gives a specific verb plus resource and immediately signals irreversibility. It further scopes the action to comments the account authored or comments by others on the account's own media, which no sibling name alone would convey.

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?

It names an explicit alternative, instagram_hide_comment, and states the condition that selects it (reversibility). The scope sentence also defines the applicability boundary — which comments this tool can act on — so an agent can decide use vs. non-use without opening other schemas.

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

Deploy Server

Other Tools