Skip to main content
Glama
unofficial-instagram-mcp

unofficial-instagram-mcp

by fanyzp

post_create

Destructive

Create a new Instagram post from local image files with a caption; set IG_DRY_RUN=true to stop just before sharing.

Instructions

Buat post baru dari file gambar lokal + caption. Dengan IG_DRY_RUN=true berhenti tepat sebelum tombol Share.

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": {
      "files": "<files>"
    },
    "name": "post_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
filesYes
captionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the risk profile is known. The description adds a genuinely useful behavioral fact: with IG_DRY_RUN=true it halts immediately before the Share action, implying UI-driven publishing that can be dry-run safely. It still omits whether a real run publishes publicly and immediately, and says nothing about failure or rate-limit behavior.

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, purpose first, the dry-run caveat second. No filler and nothing buried; every clause carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, open-world publishing tool with zero schema description coverage and no output schema, the definition is thin. It never says what a successful run produces (e.g., a media identifier), what authentication/account it acts on, or what happens to the local files, leaving meaningful gaps an agent must guess at.

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 description coverage is 0%, so the description must carry parameter meaning; it explains that 'files' are local image file paths, which the bare array-of-strings schema does not convey. However, it does not clarify that 'files' is a multi-item array (one vs many images), nor any image format, count, or caption-length constraints.

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 and resource: it creates a new post from a local image file plus a caption. That is clearly distinct from story_create or post_comment at the action level. What it does not do is explicitly name and contrast with the sibling publishing tools (story_create, story_create_poll), so 4 rather than 5.

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 guidance on when to choose this tool over story_create or the other creation tools, and no prerequisites such as account state or permissions. The only conditional mentioned is an environment flag (IG_DRY_RUN=true), which is operational advice, not usage selection guidance.

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