Skip to main content
Glama
unofficial-instagram-mcp

unofficial-instagram-mcp

story_delete

Destructive

Deletes an active Instagram story that belongs to your own account, removing currently visible content. Performs a write action unless dry-run mode is enabled.

Instructions

Hapus story aktif MILIK SENDIRI yang sedang tayang. 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_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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 readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the bar is lower, yet the description adds real context: the target must be live, and the operation is a no-op write when IG_DRY_RUN=true. That dry-run behavior is not derivable from annotations and is the most valuable disclosure here.

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 with zero filler: the destructive scope is front-loaded and the dry-run caveat follows. Nothing is repeated from the schema or annotations.

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?

With no parameters, no output schema, and annotations already covering the safety profile, the description supplies what matters: exactly which story is removed and the dry-run override. Only the absence of an explicit irreversibility statement or sibling routing keeps it below the top mark.

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?

The tool takes zero parameters, so the schema baseline is 4 and no parameter explanation is required. The description still names the IG_DRY_RUN environment flag that governs write behavior, which is useful supplementary context.

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+resource ('Hapus story' = delete story) plus scope: an active, currently-live story that belongs to the calling user ('MILIK SENDIRI', 'sedang tayang'). This distinguishes it from a generic post deletion and rules out other users' stories, though it never names a sibling tool.

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?

The 'own active story' constraint implies when the tool applies, and the closest alternative (story_create) is guessable from the name. However, no explicit when-not clause or alternative routing is given, so guidance is implied rather than stated.

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