Skip to main content
Glama
unofficial-instagram-mcp

unofficial-instagram-mcp

by fanyzp

dm_send

Destructive

Sends or replies to messages in an existing Instagram DM thread by thread ID, enabling direct message follow-ups from an AI agent.

Instructions

Kirim / balas pesan di thread DM yang sudah ada (berdasarkan threadId). AKSI TULIS: benar-benar terkirim 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": {
      "threadId": "<threadId>",
      "text": "<text>"
    },
    "name": "dm_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
threadIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.5/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/irreversible profile is known. The description still adds real value by naming the IG_DRY_RUN environment flag as the only thing preventing actual delivery. It stops short of describing rate limits, permission scope, or what comes back on success/failure, so with annotations doing most of the work a 3 fits.

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?

Two short sentences with the action and the critical dry-run caveat front-loaded; nothing is padded. Slightly telegraphic, but every clause earns its place.

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 two-parameter, non-destructive-to-data messaging tool with annotations covering the safety profile and no output schema to explain, the definition covers the essential: target, prerequisite, and real-world side effect. Missing only edge-case behavior (error when thread missing) which is minor here.

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 clarifies that threadId must identify an already-existing DM thread, which is genuinely beyond the bare schema, but says nothing about threading/reply semantics or text constraints (length, formatting). Partial compensation only.

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 (send/reply) and resource (message in an existing DM thread), and pins the addressing to threadId. It implicitly distinguishes itself from dm_send_to_user by requiring a thread that already exists, though it never names that sibling.

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 phrase 'thread DM yang sudah ada (berdasarkan threadId)' implies the prerequisite that a thread must exist first, which is useful guidance. However, it never says what to do when no thread exists (e.g., use dm_send_to_user) or when to prefer dm_check/dm_read_thread, so the agent must infer the routing.

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