Skip to main content
Glama
unofficial-instagram-mcp

unofficial-instagram-mcp

by fanyzp

dm_read_thread

Read-only

Reads one Instagram DM thread by threadId, returning the username, display name, and recent messages with direction (fromMe indicates your own account's messages). Use it to inspect conversation history.

Instructions

Baca isi 1 thread DM: username, nama, dan pesan-pesan terakhir dengan arahnya (fromMe true = pesan akun sendiri).

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>"
    },
    "name": "dm_read_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
threadIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is carried. The description adds genuinely non-redundant behavioral detail — the shape of the returned payload and the meaning of the message direction flag (fromMe true = own account) — but says nothing about whether reading marks the thread as read, how many messages come back, or what happens for an unknown threadId.

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?

A single compact sentence with no filler, front-loaded on the verb and resource, followed by the return contents and the fromMe clarification. It is efficient, though the parenthetical direction note slightly interrupts the flow.

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 low-complexity read tool with no output schema and no nested objects, the description does cover what comes back, which is the main gap-filler. However, with zero schema coverage on two parameters, the undefined limit parameter leaves a real hole an agent cannot resolve from the definition alone.

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 both parameters, and it does not: threadId is only obliquely implied by "1 thread", and limit is never explained (it must be guessed as a message count from "pesan-pesan terakhir"). No format, default, or range is given for either parameter.

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 ("Baca isi 1 thread DM") and even enumerates the returned content: username, name, and the last messages with their direction. It is distinguishable from list-style siblings because it is explicitly scoped to a single thread, though no sibling is named directly.

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?

Usage is only implied: the phrase "1 thread DM" signals that a specific threadId is required, so an agent can infer this is the read-a-single-conversation tool. There is no explicit when-to-use/when-not, no mention of dm_list_threads or dm_check as alternatives, and no stated prerequisites.

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