Skip to main content
Glama
unofficial-instagram-mcp

unofficial-instagram-mcp

story_reply

Destructive

Replies to an Instagram story as a direct message by sending specified text to a username.

Instructions

Balas story seorang user dengan teks (masuk sebagai DM). 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": {
      "username": "<username>",
      "text": "<text>"
    },
    "name": "story_reply"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
usernameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/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 write/destructive nature is partly redundant in the description. However, "AKSI TULIS kecuali IG_DRY_RUN=true" adds genuinely new context: an environment-flag dry-run mode that the agent cannot see in annotations. It still omits rate limits, permission/follow requirements, and error behavior for a destructive external write.

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, no filler, with the core action front-loaded and the write/dry-run caveat immediately after. Every clause carries information the agent needs.

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 write with no output schema and zero parameter documentation, the description is thin: it does not say what happens on success/failure, how the target story is resolved from a username, or what the dry-run mode returns instead of sending. The agent is left guessing on the most consequential details.

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?

Schema description coverage is 0%, so the description must carry the parameter burden, and it only loosely maps "seorang user" to username and "teks" to text. Critically, it never explains how the specific story is identified when only a username is supplied (latest story? any active story?), which is the key ambiguity for a story-reply call.

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 and resource ("Balas story seorang user dengan teks") and adds a delivery detail ("masuk sebagai DM") that clarifies the side effect. It is clearly distinct from story_create or post_comment, though it does not explicitly differentiate itself from the sibling dm_send, which also produces a DM.

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?

No guidance on when to use this versus dm_send, dm_send_to_user, or post_reply_to_comment, and no prerequisites (e.g., must the user have an active story, must you follow them). The only conditional given is the IG_DRY_RUN gate, which is a behavior note rather than usage routing.

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