Skip to main content
Glama
unofficial-instagram-mcp

unofficial-instagram-mcp

story_create

Destructive

Create an Instagram story from an image file or a text story when Instagram Web provides a story editor; reports clearly when the platform lacks a story entry point.

Instructions

Buat story baru: dari file gambar, atau story teks (text) bila editor teks IG web tersedia untuk akun ini. BATASAN PLATFORM: Instagram Web tidak selalu menyediakan pintu pembuatan story (terverifikasi 16 Nov 2026: akun uji tidak punya entry point story sama sekali di web); tool melaporkan itu dengan jelas bila tidak tersedia. AKSI TULIS kecuali IG_DRY_RUN=true.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "story_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
textNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the write nature is known; the description adds genuinely new context in the IG_DRY_RUN=true override and the explicit failure-reporting behavior when web story creation is unavailable. However, with destructiveHint=true it never explains the public-visibility/blast radius of posting a story or what happens to the uploaded file, leaving the most consequential behavior to the annotation alone.

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?

Front-loaded with the action and two modes, then the platform caveat, then the write warning — a sensible order with little filler. The dated verification note is slightly padded but does substantiate the limitation.

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 write tool with no output schema and two fully undocumented parameters, the definition covers the write/dry-run and failure modes well but leaves unclear what a successful call returns and how the file parameter must be supplied. Adequate, not complete.

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 carries the burden; it usefully glosses 'file' as an image file and 'text' as story text. It still omits file format (path/URL/base64), encoding, whether the two are mutually exclusive, and what occurs when neither is supplied — all relevant since required=[].

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 opens with a specific verb+resource ('Buat story baru') and enumerates the two creation modes (image file vs. text), which lets an agent distinguish it from story_create_poll and post_create without opening the schema. It stops short of naming a sibling explicitly, so differentiation is inferred rather than stated.

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

Usage Guidelines4/5

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

It gives clear preconditions for the text path ('bila editor teks IG web tersedia untuk akun ini') and warns that the entry point may be entirely absent on web, with the tool reporting that. What is missing is guidance on choosing this tool over post_create or story_create_poll, and on the file-vs-text precedence.

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