instagram-mcp-server

Comment on Media

instagram_create_comment

Posts a new top-level comment on one of your own Instagram media objects, so you can add a public comment without replying to an existing thread.

Instructions

Post a new top-level comment on one of the account's own media objects.

To answer someone else's comment use instagram_reply_to_comment instead — a reply threads under theirs and notifies them.

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": {
      "media_id": "<media_id>",
      "message": "<message>"
    },
    "name": "instagram_create_comment"
  }
}

Input Schema

Name	Required	Description	Default
`message`	Yes	Comment text. Instagram rejects repeated identical text as spam.
`media_id`	Yes	Media ID to comment on

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare the mutation profile (readOnlyHint=false, idempotentHint=false, openWorldHint=true, destructiveHint=false), so the bar is lower. The description still adds real context: the comment is top-level, it must target the account's own media, and replies behave differently by notifying the other user. It omits posting rate limits and what is returned (e.g., a comment ID), which would have pushed it higher.

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?

Two short sentences with zero filler; the primary action and its scope come first, and the routing rule follows. Every clause earns its place.

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 two-parameter mutation tool whose annotations already flag it as non-read-only and non-idempotent, the definition covers the essentials. The only meaningful gap is that there is no output schema and the description doesn't say what a successful call returns, though that is a minor omission for this tool class.

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 both parameters carry their own descriptions, including the 2200-character cap and the spam-rejection note. The description adds no meaning beyond media_id and message, which is acceptable given the schema does the work, but it earns only the baseline.

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 gives a specific verb and resource ("Post a new top-level comment") and adds the crucial scope qualifier "on one of the account's own media objects," plus the contrast with threaded replies. An agent can distinguish this from instagram_reply_to_comment without opening either schema.

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 explicitly names the alternative (instagram_reply_to_comment) and states the condition that selects it: answering someone else's comment, because a reply threads under theirs and notifies them. That is a concrete when-to-use/when-not-to-use rule rather than implied guidance.

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

Deploy Server