Skip to main content
Glama
unofficial-instagram-mcp

unofficial-instagram-mcp

by fanyzp

post_save

Destructive

Saves (bookmarks) an Instagram post by URL; repeated calls are idempotent, and writes are skipped when IG_DRY_RUN=true.

Instructions

Simpan (bookmark) sebuah post. Idempotent. 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_save"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true. The description adds real value beyond that: it states the operation is idempotent (so retries are safe) and that it is a WRITE ACTION unless IG_DRY_RUN=true, which explains a runtime mode the annotations cannot encode. It does not contradict the write annotation, though it could note that a bookmark is low-risk despite the destructive hint.

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?

Three short, front-loaded sentences with no filler; the core action comes first and the operational caveats follow. The only friction is that it is written in Indonesian while the surrounding tool catalog uses English.

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 one-parameter mutation tool it covers the essentials an agent most needs (idempotency, write semantics, dry-run mode), but it leaves the url format undefined and gives no hint about auth requirements or what a successful call returns. Adequate, with clear gaps.

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?

The single required parameter 'url' has 0% schema description coverage, and the description only refers to "sebuah post" without saying whether url is a post permalink, shortcode, or media id. With one undocumented parameter, the description needed to compensate and does not.

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 gives a specific verb plus resource, "Simpan (bookmark) sebuah post", and clarifies the operation is a write. It distinguishes itself from siblings such as post_like or post_comment by naming the bookmark semantics, though it never explicitly contrasts itself with those siblings.

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 learns this is the tool for bookmarking a post and that a dry-run env flag changes behavior, but there is no explicit when-to-use versus alternatives, no prerequisite/auth note, and no statement of when not to call it.

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