Skip to main content
Glama

Social0

list_inbox_dms

Read-onlyIdempotent

List direct-message conversations for connected accounts that support DMs (X and Bluesky today). Returns conversation_id + account_id needed to open or reply to a thread.

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

Input Schema

NameRequiredDescriptionDefault
freshNoBypass warm cache and re-read the platform APIs. Entries younger than 90s are still served from cache.
limitNo
rangeNoLookback window. Use custom with since/until.7d
sinceNoISO 8601 start (range=custom)
untilNoISO 8601 end (range=custom)
beforeNoCursor from a previous response's next_before
accountNoConnected account UUID or unambiguous platform name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, non-destructive, open-world operation, so the safety profile is covered. The description adds genuine context beyond that: platform coverage is limited to DM-capable accounts (X and Bluesky today), and it discloses the key fields returned (conversation_id + account_id), which matters because there is no output schema. It does not, however, mention pagination behavior or cache semantics, which remain only in the schema.

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 sentences, both front-loaded with the essential information, and no redundant restatement of the tool name or annotations. Every clause earns its place: the first establishes scope, the second establishes downstream use.

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 read-only listing tool with rich annotations, this is nearly complete: it covers platform scope and return identifiers, and the schema handles the rest. The missing piece is pagination guidance — the 'before' cursor exists but the description never says results may be paged, which an agent needs to know to fetch a full inbox.

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 86%, so the schema already documents fresh, range, since/until, before, and account. The description adds no parameter-level meaning beyond what the schema supplies — it does not explain 'limit' semantics or how 'account' interacts with platform support. Baseline 3 is appropriate when the schema carries this burden.

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 gives a specific verb ('List') and resource ('direct-message conversations'), and adds a scope qualifier — connected accounts that support DMs, naming X and Bluesky. This is clearly distinguishable from sibling list_inbox_comments (comments vs DMs) and get_inbox_dm_thread (which opens one thread rather than listing conversations).

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 second sentence hints at the workflow by saying the returned conversation_id and account_id are needed 'to open or reply to a thread', which implicitly points to get_inbox_dm_thread or reply_to_dm as follow-ups. However, it never explicitly states when to use this versus list_inbox_comments, nor does it state prerequisites such as needing a connected DM-capable account before calling.

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.