Skip to main content
Glama
owlpost

owlpost

get_conversation

Read-onlyIdempotent

Retrieve every message in the same email thread as a given message, ordered oldest first. Identify the seed by Message-ID or folder and UID; returns envelopes only, not message bodies.

Instructions

Return every message in the same conversation as a given message, oldest first.

On Gmail this uses the X-GM-THRID thread id across All Mail. Elsewhere it follows the Message-ID / In-Reply-To / References graph across the inbox, sent, archive, all-mail and drafts folders, so your own replies are included. Returns envelopes (no bodies); use read_email for content. Identify the seed message with either message_id, or folder + uid.

Args: account: Account name from list_accounts. message_id: Message-ID header of any message in the thread, including angle brackets. folder: Folder of the seed message (used with uid). uid: UID of the seed message (used with folder).

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

Input Schema

NameRequiredDescriptionDefault
uidNo
folderNo
accountYes
message_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.0
    • addedOutput schema / $defs
      Added value: +{
      +  "Address": {
      +    "properties": {
      +      "email": {
      +        "title": "Email",
      +        "type": "string"
      +      },
      +      "name": {
      +        "title": "Name",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "name",
      +      "email"
      +    ],
      +    "title": "Address",
      +    "type": "object"
      +  },
      +  "Envelope": {
      +    "properties": {
      +      "bcc": {
      +        "items": {
      +          "$ref": "#/$defs/Address"
      +        },
      +        "title": "Bcc",
      +        "type": "array"
      +      },
      +      "cc": {
      +        "items": {
      +          "$ref": "#/$defs/Address"
      +        },
      +        "title": "Cc",
      +        "type": "array"
      +      },
      +      "date": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "title": "Date"
      +      },
      +      "date_iso": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "title": "Date Iso"
      +      },
      +      "flagged": {
      +        "title": "Flagged",
      +        "type": "boolean"
      +      },
      +      "flags": {
      +        "items": {
      +          "type": "string"
      +        },
      +        "title": "Flags",
      +        "type": "array"
      +      },
      +      "folder": {
      +        "title": "Folder",
      +        "type": "string"
      +      },
      +      "from": {
      +        "items": {
      +          "$ref": "#/$defs/Address"
      +        },
      +        "title": "From",
      +        "type": "array"
      +      },
      +      "in_reply_to": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "title": "In Reply To"
      +      },
      +      "message_id": {
      +        "title": "Message Id",
      +        "type": "string"
      +      },
      +      "references": {
      +        "items": {
      +          "type": "string"
      +        },
      +        "title": "References",
      +        "type": "array"
      +      },
      +      "seen": {
      +        "title": "Seen",
      +        "type": "boolean"
      +      },
      +      "size": {
      +        "anyOf": [
      +          {
      +            "type": "integer"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "title": "Size"
      +      },
      +      "subject": {
      +        "title": "Subject",
      +        "type": "string"
      +      },
      +      "to": {
      +        "items": {
      +          "$ref": "#/$defs/Address"
      +        },
      +        "title": "To",
      +        "type": "array"
      +      },
      +      "uid": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "type": "null"
      +          }
      +        ],
      +        "title": "Uid"
      +      }
      +    },
      +    "required": [
      +      "uid",
      +      "folder",
      +      "message_id",
      +      "in_reply_to",
      +      "references",
      +      "subject",
      +      "from",
      +      "to",
      +      "cc",
      +      "bcc",
      +      "date",
      +      "date_iso",
      +      "flags",
      +      "seen",
      +      "flagged",
      +      "size"
      +    ],
      +    "title": "Envelope",
      +    "type": "object"
      +  }
      +}
    • addedOutput schema / properties / result / items / $ref
      Added value: +"#/$defs/Envelope"
    • removedOutput schema / properties / result / items / additionalProperties
      Removed value: -true
    • removedOutput schema / properties / result / items / type
      Removed value: -"object"
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing implementation behavior: Gmail uses X-GM-THRID across All Mail, other providers traverse the Message-ID/In-Reply-To/References graph across inbox, sent, archive, all-mail and drafts. It also states the return shape (envelopes, no bodies), which the readOnly/idempotent hints do not convey.

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 the core action and ordering, then provider behavior, then an Args block. Slightly redundant in restating parameter purposes after the prose, but every line carries information and there is no filler.

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 four-parameter, provider-varying lookup tool this covers the scope of the traversal, the seed identification paths, and the envelope-only return, so an agent can call it correctly without opening the schema. Output schema exists, so no further return-value explanation is required.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the full burden and does: it documents all four parameters, including the format detail that message_id includes angle brackets, and the pairing semantics of folder + uid. It also states the seed may be identified by either message_id OR folder+uid, a mutual-exclusivity rule the schema does not encode.

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 (return every message in the same conversation as a given message) plus an ordering guarantee (oldest first). It is clearly distinguishable from siblings like read_email and search_messages, which is reinforced by naming read_email for body content.

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 a clear use context (thread/conversation expansion) and an explicit alternative for a different need: 'use read_email for content.' It does not explicitly contrast with search_messages or state when-not to use it, so it falls short of full when/when-not/alternatives coverage.

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