list_draftsList draft emails newest first across one or more connected Gmail or IMAP accounts, so you can review and manage pending messages by account.
List draft emails (newest first) for one or more accounts.
| Name | Required | Description | Default |
|---|---|---|---|
| account | No | Which mailbox(es): an alias, an email address, a list of them, or "all". Omit to use ALL connected accounts. No accounts connected yet. | |
| maxResults | No | Max drafts per account (default 10). |
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavior ('newest first') and multi-account scope, but omits return shape, pagination, and auth/rate details.
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 sentence, front-loaded with verb and resource, with no filler. It is appropriately sized for a simple read-only list tool.
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?
For a simple read-only tool, the description plus full schema coverage and annotations is nearly sufficient for correct invocation. It does not describe returned draft fields despite there being no output schema, but that is a minor gap.
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 100%, and the schema documents account forms ('all', omit, list) plus maxResults default and maximum. The description only reinforces 'one or more accounts' and sorting; it adds no parameter syntax or constraints beyond the schema.
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 ('List'), resource ('draft emails'), ordering ('newest first'), and scope ('one or more accounts'). The resource distinguishes it from create_draft, delete_draft, and email search tools, so an agent can select it directly.
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?
No when-to-use, when-not-to-use, or alternative-tool guidance is provided. It does not explain when to use this instead of search_emails or how it relates to create_draft/delete_draft; usage is only implied by the purpose.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.