Fetch a page of conversation messages from an email thread by thread ID, with pagination and bounded body content.
Fetch a page of conversation messages with bounded body content.
| Name | Required | Description | Default |
|---|---|---|---|
| pageSize | No | ||
| threadId | Yes | ||
| accountId | No | Account to operate on. Optional when exactly one account is connected. | |
| pageToken | No | ||
| bodyFormat | No |
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes |
Changes observed during successful MCP inspections.
v0.11.1Output schema / $schemaRemoved value: -"http://json-schema.org/draft-07/schema#"v0.11.0Input schema / properties / bodyFormatAdded value: +{
+ "enum": [
+ "text",
+ "html",
+ "both",
+ "none"
+ ],
+ "type": "string"
+}Input schema / properties / pageSizeAdded value: +{
+ "maximum": 25,
+ "minimum": 1,
+ "type": "integer"
+}Input schema / properties / pageTokenAdded value: +{
+ "minLength": 1,
+ "type": "string"
+}Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "data": {
+ "additionalProperties": false,
+ "properties": {
+ "id": {
+ "type": "string"
+ },
+ "messages": {
+ "items": {
+ "additionalProperties": true,
+ "properties": {
+ "accountId": {
+ "type": "string"
+ },
+ "attachments": {
+ "items": {
+ "additionalProperties": true,
+ "properties": {
+ "filename": {
+ "type": "string"
+ },
+ "id": {
+ "type": "string"
+ },
+ "mimeType": {
+ "type": "string"
+ },
+ "sizeBytes": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "id",
+ "filename",
+ "mimeType",
+ "sizeBytes"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "body": {
+ "additionalProperties": false,
+ "properties": {
+ "html": {
+ "type": "string"
+ },
+ "text": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "bodyTruncation": {
+ "additionalProperties": {
+ "additionalProperties": false,
+ "properties": {
+ "nextOffset": {
+ "type": "number"
+ },
+ "totalChars": {
+ "type": "number"
+ }
+ },
+ "required": [
+ "totalChars"
+ ],
+ "type": "object"
+ },
+ "type": "object"
+ },
+ "date": {
+ "type": "string"
+ },
+ "flags": {
+ "additionalProperties": true,
+ "properties": {
+ "draft": {
+ "type": "boolean"
+ },
+ "read": {
+ "type": "boolean"
+ },
+ "starred": {
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "read",
+ "starred",
+ "draft"
+ ],
+ "type": "object"
+ },
+ "id": {
+ "type": "string"
+ },
+ "subject": {
+ "type": "string"
+ },
+ "threadId": {
+ "type": "string"
+ },
+ "to": {
+ "items": {
+ "additionalProperties": true,
+ "properties": {
+ "email": {
+ "type": "string"
+ },
+ "name": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "email"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "id",
+ "threadId",
+ "accountId",
+ "to",
+ "subject",
+ "date",
+ "flags"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "nextPageToken": {
+ "type": "string"
+ },
+ "subject": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "id",
+ "subject",
+ "messages"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "data"
+ ],
+ "type": "object"
+}v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description adds useful context that content is paginated ('a page') and body content is 'bounded', but says nothing about how bounding works, defaults, or traversal behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single, front-loaded sentence with no filler. It is efficient, though arguably too terse given the number of undocumented parameters.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so returns need not be described, but four of five parameters (including the pageToken pagination contract and the bodyFormat enum) have no explanation anywhere. For a paginated read tool with this many options, the description is not sufficient to invoke it confidently.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is only 20% (only accountId documented), leaving pageSize, pageToken, bodyFormat, and threadId without schema-level explanation. The description adds no parameter detail at all, so it fails to compensate for the coverage gap despite pagination and body-format being non-obvious.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Fetch) and resource (a page of conversation messages), and the 'bounded body content' phrase signals it returns message bodies rather than metadata only. It is clearly distinguishable from get_email_body and get_email, though it does not name those siblings explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this versus get_email, get_email_body, or search_emails. No prerequisites, no exclusions, no conditions for selecting this tool over its many siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.