Skip to main content
Glama
inssist

@inssist/mcp

Official
by inssist
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

DM read

dm_read
Read-only

Read messages from an Instagram DM conversation, returned oldest first. Increase the limit parameter to fetch older messages, up to 200 per request. Read-only.

Instructions

Read a DM conversation's messages, oldest first. Returns the newest limit messages; raise limit to reach older ones. has_more means older messages were cut off. Read-only. (Requires INSSIST PRO.)

Input Schema

NameRequiredDescriptionDefault
limitNoHow many of the newest messages to return, 1-200 (default 20).
instantNoOptional. Skip INSSIST's action pacing and run now — use only when the user asked for an unspaced or burst action.
instanceNoOptional. Browser instance id from account_info; defaults to the active one.
thread_idYesConversation id from dm_list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "How many of the newest messages to return, 1-200 (default 20).",
+  "type": "number"
+}
  2. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description's 'Read-only' is consistent. Beyond that, it discloses pagination behavior (returns newest limit, raise limit to reach older, has_more flag) and a requirement (INSSIST PRO). This adds useful context about how the tool behaves, beyond what annotations capture, though it doesn't describe the full return format.

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?

The description is three concise sentences with no filler. It front-loads the core purpose, then adds pagination details and the read-only/pro requirement. Every sentence serves a purpose, and the structure is easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the tool's behavior (ordering, pagination), disclaims side effects (read-only), and notes the PRO requirement. Combined with a fully documented schema, an agent has enough to call it correctly without additional context. No output schema exists, so return format is not expected here.

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 100%, so all parameters are well described individually. The description adds meaning to 'limit' by explaining it controls pagination (raise to reach older messages), which is not fully captured in the schema's 'How many of the newest messages to return'. This augments the parameter's functional purpose, earning a score above baseline.

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 clearly states the tool reads DM conversation messages, specifies ordering (oldest first), and notes it is read-only. This distinguishes it from sibling tools like dm_send or dm_mark_seen. The verb 'read' and resource 'DM conversation's messages' are specific and unambiguous.

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 description implies usage (when you need to read messages) but does not explicitly state when to use this vs. alternatives like dm_list (to find thread_id) or dm_requests (for requests). It lacks exclusions or explicit 'when not to use' guidance, though the read-only nature hints at distinctions.

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

Deploy Server

Other Tools