Skip to main content
Glama
Sign In
Instagram MCP Server

Instagram MCP Server

by luminarylane
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ig_delete_comment

Remove a comment from your Instagram post by specifying its comment ID.

Instructions

Delete a comment on one of your Instagram posts.

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": {
      "commentId": "<commentId>"
    },
    "name": "ig_delete_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountIdNoInstagram Business Account ID. Falls back to INSTAGRAM_BUSINESS_ACCOUNT_ID env var.
commentIdYesID of the comment to delete
accessTokenNoInstagram access token. Falls back to INSTAGRAM_ACCESS_TOKEN env var.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.6.6

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses the destructive nature ('Delete'), but does not mention whether deletion is irreversible, what permissions are required, or any rate limits. For a mutation tool, more detail is needed.

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?

Single sentence, no wasted words. Front-loaded with the core action. Every word serves a purpose.

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 deletion tool with a well-documented schema (100% coverage), the description is mostly adequate. However, it lacks usage guidance and behavioral details that would fully inform an AI agent, especially given the absence of an output schema and annotations.

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%, and the schema already documents each parameter (accountId, commentId, accessToken) including fallback behavior for accountId and accessToken. The description adds no additional meaning beyond the schema, so a baseline of 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 'Delete a comment on one of your Instagram posts.' It uses a specific verb ('Delete') and resource ('comment on Instagram post'), and it effectively distinguishes itself from sibling tools like ig_get_comments (for reading) and ig_reply_comment (for writing).

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 explicit guidance on when to use this tool versus alternatives, nor any mention of prerequisites (e.g., needing the comment to exist, ownership requirements). The description only states the action without contextualizing when it is appropriate.

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