Skip to main content
Glama
unofficial-instagram-mcp

unofficial-instagram-mcp

by fanyzp

post_comment

Destructive

Adds a new comment to an Instagram post or reel using its URL and specified text; performs a write action unless IG_DRY_RUN=true.

Instructions

Komentar baru di post/reel dari URL-nya. AKSI TULIS kecuali IG_DRY_RUN=true.

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": {
      "url": "<url>",
      "text": "<text>"
    },
    "name": "post_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
textYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the write and open-world nature are covered. The description adds a valuable detail the annotations do not carry: the IG_DRY_RUN=true environment flag turns the action into a dry run, which meaningfully changes the effect of the call. It still omits side effects such as rate limits or failure modes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is two short sentences with the action up front and the dry-run caveat second, and it contains no filler. The brevity comes close to under-specification, but no sentence is wasted.

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 two-parameter write tool whose annotations already establish safety characteristics, the description covers the core action and the dry-run modifier. It leaves gaps around parameter formats. Given the minimal schema and no output schema, those gaps are significant enough to prevent a complete rating.

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 description coverage is 0%, so the description is responsible for documenting the two parameters. It only indicates that the URL identifies the post, and says nothing about the format of the URL or what the text parameter accepts (mentions, hashtags, length limits).

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?

The description names a concrete verb+resource (posting a comment on a post/reel) and specifies the input source as the URL. It does not explicitly distinguish itself from the close sibling post_reply_to_comment, leaving that boundary to inference.

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?

There is no statement of when to use this tool versus alternatives such as post_reply_to_comment or other post tools. The only usage-adjacent information is that the target is identified by URL, and that is implied rather than prescribed.

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