Skip to main content
Glama

Read conversation

get_thread
Read-only

Retrieve all messages in an email conversation across folders, ordered oldest first, with each body limited to its new text and no quoted history.

Instructions

Get every message in a conversation (across folders), oldest first. Each body contains only the new text of that message, without quoted history.

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

Input Schema

NameRequiredDescriptionDefault
messageIdNoAny message in the conversation
maxBodyCharsNoPer-message body limit (default 4000)
conversationIdNoConversation ID (alternative to messageId)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: deterministic oldest-first ordering and the fact that each body contains only new text without quoted history, which affects how an agent should consume results. It does not mention pagination, truncation signaling for maxBodyChars, or what happens when no identifier is supplied.

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 with no filler. The retrieval scope is front-loaded and the body-content caveat follows as a secondary but necessary clarification.

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 three-parameter read tool with full schema coverage and safety annotations, ordering and body semantics are adequately covered. The notable gap is that required parameters are zero while messageId and conversationId are alternatives, so an agent is not told that one identifier is needed or how the two interact.

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%, so all three parameters (messageId, conversationId, maxBodyChars) are already documented, including the default and bounds for the body limit. The description adds only the indirect hint that a conversation spans folders; it does not explain the messageId-vs-conversationId alternative or that at least one identifier must be provided.

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 ('Get every message in a conversation') plus scope ('across folders') and ordering ('oldest first'). This clearly separates it from the single-message sibling get_message and from list_messages without needing to name them.

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 'across folders' clause implies the tool's niche (full conversation retrieval rather than per-folder listing), but there is no explicit when-to-use statement, no exclusion of alternatives such as get_message or list_messages, and no prerequisites. Usage must be inferred from the scope phrasing alone.

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