Skip to main content
Glama
unofficial-instagram-mcp

unofficial-instagram-mcp

by fanyzp

comment_like

Destructive

Like a specific Instagram comment by matching its text at a given post URL, enabling targeted engagement without manual searching.

Instructions

Like satu komentar spesifik (cari yang memuat teks match). 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>",
      "match": "<match>"
    },
    "name": "comment_like"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
matchYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already flag readOnlyHint=false, destructiveHint=true and openWorldHint=true, but the description adds genuinely new information: the action is a write unless IG_DRY_RUN=true. It does not disclose what happens on zero or multiple matches, or whether a like can be undone — notable gaps given destructiveHint is set.

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?

Two tight sentences, front-loaded with the action and the targeting rule, with the dry-run caveat placed last where it belongs. No wasted wording, though the mixed-language phrasing is slightly terse for a non-Indonesian reader.

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 destructive-tagged mutation with no output schema and zero schema description coverage, the definition covers the targeting rule and the dry-run switch but omits failure behavior, match ambiguity handling, and the meaning of `url`. Adequate but with clear gaps.

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 0%, so the description must compensate. It gives real meaning for `match` (a substring used to locate the target comment), but `url` is left unexplained — presumably the post containing the comment — so only half the parameters are clarified.

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?

States a specific verb+resource ("Like satu komentar spesifik") and clarifies the targeting mechanism — the comment is located by text contained in `match`. That distinguishes it from a generic like, though it never names the sibling `post_like` to make the comment-vs-post distinction explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: supply a URL and a text snippet that identifies the comment. There is no explicit statement of when to prefer this over `post_like` or what to do when several comments match the same text, so the agent must infer the selection logic.

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