Skip to main content
Glama
unofficial-instagram-mcp

unofficial-instagram-mcp

by fanyzp

dm_check

Read-only

Identifies Instagram direct message threads whose latest message is from the other person, helping you see which conversations need a reply without sending any messages.

Instructions

Cek thread mana yang pesan terakhirnya dari lawan bicara (perlu dibalas). Baca saja, tidak membalas apa pun.

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": "dm_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

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, and the description reinforces this with 'Baca saja, tidak membalas apa pun' while adding the meaningful filtering semantics (only threads where the counterpart spoke last). It still omits what the response looks like (thread list, message snippets, ordering) and whether results are truncated.

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 core filtering semantic front-loaded and the read-only reassurance second. No filler, though the extreme brevity leaves gaps that another sentence could have closed.

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?

With no output schema, the description should indicate what an agent receives back (e.g. a list of thread IDs/participants). It covers scope and safety adequately but is incomplete on return shape for a tool whose whole value is the filtered result set.

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?

The single parameter 'limit' has 0% schema description coverage, and the description says nothing about it. The name is guessable, but the description fails to compensate for the low coverage or state default/max values.

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: identifying DM threads whose last message came from the counterpart (i.e. awaiting a reply). This is a distinct scope from dm_list_threads or dm_read_thread, though it does not name any sibling explicitly, so an agent must infer the boundary.

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 'perlu dibalas' (needs replying) implies the use case: finding unanswered conversations before replying. However, there is no explicit when-to-use/when-not or pointer to dm_list_threads versus dm_read_thread versus dm_send, leaving routing to inference.

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