Skip to main content
Glama
agentisend

agentisend

List received threads

list_threads
Read-onlyIdempotent

Group received mail into conversations by Message-ID, In-Reply-To and References, newest thread first, with each row showing the verdict of its newest message. Use it to review conversation history.

Instructions

Purpose: group received mail into conversations by Message-ID, In-Reply-To and References, newest thread first. Each row carries the verdict of its newest message. Held messages are left out unless include_held is true. NOT for: reading a message body (get_received_email) or sending a reply (reply_to_email). A thread with no Message-ID is listed under its own received id. Returns: data, has_more, and next_cursor. Each row has the thread id, subject, participants, message_count, last_received_at, latest_id and verdict.

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_threads"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size (1-100).
cursorNonext_cursor from the previous page. Omit for the first page.
include_heldNoSet true to include threads whose messages are still held. Omitted, held messages are left out.

Output Schema

NameRequiredDescriptionDefault
dataNoThis page of rows.
errorNoPresent instead of the fields above when the call was refused: code, message, fix, docs_url, retryable and, when waiting helps, retry_after_seconds.
has_moreNoTrue when another page follows.
next_cursorNoPass back as cursor for the next page; null on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so safety is covered; the description still adds real behavior: thread ordering, the rule that each row carries its newest message's verdict, default exclusion of held messages, and the fallback for messages with no Message-ID. Slight redundancy in restating the held-message exclusion, which the schema also documents.

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?

Front-loaded with Purpose / NOT for / Returns blocks and free of filler. The Returns paragraph partly duplicates the output schema, so a sentence or two is not strictly earning its place.

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?

For a read-only list tool with rich annotations, full schema coverage and an output schema, the description supplies the one thing structured fields cannot: the grouping and fallback logic. Nothing an agent needs to call it correctly is missing.

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 100% and every parameter is already described there, including limit bounds, cursor usage, and include_held. The description's 'held messages are left out unless include_held is true' restates the schema rather than adding new meaning, so baseline 3 applies.

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 (group received mail into conversations) plus the exact algorithm (Message-ID, In-Reply-To, References) and ordering (newest thread first). It also names siblings it is not (get_received_email, reply_to_email), so it is distinguishable at a glance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit NOT-for clause routes the agent to the correct alternative for reading a body and for replying. The include_held condition tells the agent exactly when to flip a parameter rather than leaving it to inference.

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