Scribe Mail

List emails

list_emails

Read-onlyIdempotent

List the workspace's teammate email addresses, primary and aliases, newest first, each with its id, address, primary flag and owning teammate_id. Use it to get the email id that add_signature_recipients, remove_signature_recipients, update_email, delete_email, install_signature_for_email and send_test_email take. Use list_teammates instead when you also need smart-field values: it embeds each teammate's emails too. There is no address search: filter by teammate_id, or page through and match address. Deleted emails and teammates are excluded. Read-only; needs the emails:read scope. Returns one page (default 50, max 100); set auto_paginate to fetch up to max_pages, and truncated: true means more remain.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	1-based page (default 1).
`limit`	No	Page size, 1–100 (default 50).
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`max_pages`	No	Page cap when auto_paginate is true (default 5).
`teammate_id`	No	Filter to a single teammate's emails by their UUID (the `id` from list_teammates). An unknown id returns an empty list, not an error.
`auto_paginate`	No	Fetch multiple pages up to `max_pages` (default false).

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes
`truncated`	Yes	True when auto_paginate stopped at max_pages with more results remaining.
`pagination`	Yes
`pages_fetched`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 16, 2026

changedInput schema / properties / teammate_id / description

Previous value: -"Filter to a single teammate's emails by their UUID (the teammate `id`)."New value: +"Filter to a single teammate's emails by their UUID (the `id` from list_teammates). An unknown id returns an empty list, not an error."

First observedOct 16, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds beyond them: the required emails:read scope, exclusion of deleted emails and teammates, page-size defaults (50/100), the auto_paginate+max_pages behavior, and the meaning of `truncated: true`.

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?

Dense but every sentence earns its place: scope/return shape first, then consumer tools, then the alternative, then the no-search constraint, then pagination. 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?

Covers the identity of the resource, filtering limits, pagination semantics, scope/auth, and sibling routing; with an output schema present it correctly avoids re-explaining the raw return payload. Nothing needed to call it correctly is missing.

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

Parameters4/5

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

Schema description coverage is 100%, so baseline is 3; the description adds meaning by explaining that filtering is by `teammate_id` only, that paging plus matching `address` is the search substitute, and what `truncated` signals. It stops short of documenting every parameter, so a 4 rather than 5.

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+resource ('List the workspace's teammate email addresses, primary and aliases') and enumerates the returned fields (`id`, `address`, `primary`, `teammate_id`). It explicitly distinguishes itself from the sibling list_teammates and names the downstream tools that consume the returned `id`.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use (get the email `id` for add/remove_signature_recipients, update_email, delete_email, etc.), a named alternative with its selection condition (list_teammates when smart-field values are also needed), and a negative constraint ('There is no address search') with a workaround.

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

All Scribe Mail tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.