Skip to main content
Glama
unofficial-instagram-mcp

unofficial-instagram-mcp

by fanyzp

post_delete

Destructive

Deletes one of your own Instagram posts by its URL, refusing if the signed-in account is not the author; a write action unless dry-run mode is enabled.

Instructions

Hapus post MILIK SENDIRI dari URL-nya. Menolak bila penulisnya bukan akun yang login. 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_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds real context beyond them: an authorization check tied to the logged-in account, and the IG_DRY_RUN=true escape hatch that downgrades the write. It does not discuss irreversibility of the deleted post or side effects on comments/likes, which keeps it below a 5.

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?

Three short sentences, each doing distinct work: action, ownership restriction, and write-action/dry-run caveat. The critical constraint is front-loaded and there is no filler.

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?

For a one-parameter destructive tool with safety annotations and no output schema, the description covers the essentials: what is deleted, on whose authority, and how to run it non-destructively. Minor gaps around the return value and the fate of associated comments are acceptable given the annotations already flag destruction.

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?

Schema coverage is 0% and the single 'url' parameter is completely undocumented in the schema, so the description must carry the load. It does: the URL identifies the target post and must be a post the caller owns, which is exactly the semantics an agent needs to supply it correctly.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a precise verb and resource ('Hapus post' = delete post) and narrows the scope to 'MILIK SENDIRI' (your own) posts identified by URL. That scope alone separates it from siblings like post_create, post_comment, or story_delete, so an agent can pick it without opening the schema.

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 a clear precondition for use: the post must belong to the currently logged-in account, and the call is rejected otherwise. It does not name an alternative tool for deleting stories or other resources, nor explain what to do on rejection, so it stops short of full when/when-not routing.

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