Skip to main content
Glama

Social0

get_inbox_dm_thread

Read-onlyIdempotent

Read the messages in one DM conversation. Call list_inbox_dms first to get conversation_id.

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": {
      "conversation_id": "<conversation_id>",
      "account": "<account>"
    },
    "name": "get_inbox_dm_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
freshNo
accountYesConnected account UUID or platform name that owns the conversation
peer_idNoOnly needed when the platform omits it
conversation_idYesconversation_id from list_inbox_dms

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds only the call-ordering prerequisite; it says nothing about message ordering, pagination, result limits, or what 'fresh' changes, which are the remaining behavioral unknowns for a thread read.

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?

Two short sentences, the core action first and the prerequisite second. Nothing extraneous and nothing buried.

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 read-only tool with no output schema, the description is close to sufficient, but it leaves the 'fresh' flag and thread-read behavior (ordering/pagination) undefined. Those are the details an agent would still need to call this confidently.

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 coverage is 75% and the description only reinforces where conversation_id comes from, which the schema already states. The one parameter with no schema description — 'fresh' — is also left unexplained here, so the description does not compensate for the coverage gap.

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?

States a specific verb and resource — 'Read the messages in one DM conversation' — which cleanly separates it from list_inbox_dms (list conversations) and reply_to_dm (write). 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?

Gives an explicit prerequisite: call list_inbox_dms first to obtain conversation_id. It does not say when to avoid this tool or how it relates to reply_to_dm beyond the implied read/write split, so it stops short of full when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.