Skip to main content
Glama

Get a conversation

get_conversation
Read-only

Use this when the user wants to read one email thread or LinkedIn chat in full. Returns every message, oldest first: for email, each message's sender, recipients, subject, HTML body, labels and attachment names; for LinkedIn, each message's text, sender and time. Send the conversation's channel with its id. Free.

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": {
      "conversationId": "<conversationId>",
      "channel": "<channel>"
    },
    "name": "get_conversation"
  }
}

Input Schema

NameRequiredDescriptionDefault
channelYes`email` or `linkedin`.
conversationIdYesThe conversation's `id`, as the conversations list gives it.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds real value beyond that with message ordering ('oldest first'), the per-channel payload contents, and the cost note ('Free'). It omits edge behavior such as what happens for a missing/unauthorized conversation id or whether bodies are truncated.

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?

Three sentences, front-loaded with the trigger condition, then returns, then the calling instruction. The enumeration of returned fields is dense but each item carries information the agent would otherwise have to guess without an output schema.

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?

With no output schema, the description compensates by spelling out the shape of returned messages per channel, plus ordering and cost. For a two-parameter read tool with full schema coverage and clear annotations, nothing essential to correct invocation 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 both parameters are documented in-schema, including the enum for channel. The description's 'Send the conversation's channel with its id' only restates the required pairing, adding no format or sourcing detail beyond the schema. 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 ('read one email thread or LinkedIn chat in full') and bounds scope to a single conversation, which clearly separates it from list/count siblings and from update_conversation. The two supported channels are named explicitly.

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?

Opens with an explicit trigger condition ('Use this when the user wants to read one...'), giving the agent a clear selection signal. It does not name a when-not case or point to an alternative for related needs (e.g., listing conversations), so it stops short of full routing 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.

Resources