Skip to main content
Glama
unofficial-instagram-mcp

unofficial-instagram-mcp

by fanyzp

post_like

Destructive

Likes an Instagram post or reel using its URL and reports if it was already liked; performs a write action unless dry-run mode is enabled.

Instructions

Like sebuah post/reel dari URL-nya. Idempotent: kalau sudah di-like, dilaporkan alreadyLiked. 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>"
    },
    "name": "post_like"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare the write/destructive/open-world profile, so the description sensibly adds the things annotations cannot: idempotency, the alreadyLiked signal, and that execution is gated by the IG_DRY_RUN=true environment variable. That is real context beyond structured fields, though it doesn't cover auth requirements or rate limits.

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?

Three short clauses, front-loaded with the action, then idempotency semantics, then the write/dry-run caveat. No filler and no repetition of schema or annotation content.

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 one-parameter, no-output-schema tool, the definition covers purpose, idempotency, return signal, and the dry-run gate, which is enough to call it correctly. It omits edge cases such as behavior on private posts or invalid URLs, so it is not exhaustive.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With a single parameter and 0% schema description coverage, the description must carry the meaning, and 'dari URL-nya' does clarify that the string is the URL of the target post/reel. It adds useful framing but no format examples or constraints on what a valid URL looks like.

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 states a specific verb (like) and resource (post/reel) and identifies the input as a URL, which implicitly separates it from the comment-oriented sibling comment_like. It never names an explicit alternative, so it stops just short of the full sibling-differentiation bar.

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 only implied: the agent can infer 'use this to like a post or reel,' but there is no explicit when-to-use or when-not-to-use guidance and no named alternative (e.g., unlike/comment_like). The dry-run caveat is behavioral, not routing guidance.

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