Skip to main content
Glama
Sign In
Instagram MCP Server

Instagram MCP Server

by luminarylane
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ig_reply_comment

Reply to an Instagram comment by providing the comment ID and your reply message.

Instructions

Reply to a comment on an Instagram post.

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>",
      "message": "<message>"
    },
    "name": "ig_reply_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageYesReply text
accountIdNoInstagram Business Account ID. Falls back to INSTAGRAM_BUSINESS_ACCOUNT_ID env var.
commentIdYesID of the comment to reply to
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 must fully disclose behavioral traits. It only states 'Reply to a comment' but does not mention authentication requirements, rate limits, or any side effects beyond the basic action.

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?

The single-sentence description is front-loaded and contains no unnecessary words, earning its place efficiently.

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 mutation tool with no output schema, the description is minimally complete but lacks context about prerequisites (e.g., needing an Instagram Business Account) beyond what's inferred from schema field descriptions.

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 description coverage is 100%, so the schema already describes all parameters. The description adds no extra semantics beyond what the schema provides, resulting in a baseline score of 3.

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 'Reply to a comment on an Instagram post' uses a specific verb ('Reply') and resource ('comment on an Instagram post'), clearly indicating the action. It distinguishes from sibling tools like 'ig_delete_comment'.

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 guidance is provided on when to use this tool versus alternatives (e.g., deleting a comment). The context is implied but not explicit.

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