Skip to main content
Glama
Cresca MCP Server

Cresca MCP Server

List emails

list_emails
Read-onlyIdempotent

Review sent email activity by listing messages newest first with cursor pagination; bodies are omitted, so fetch full content separately when needed.

Instructions

GET /emails. Lists emails sent through the API, newest first, without html/text bodies (use get_email for those). Cursor pagination: while has_more is true, pass the id of the last item as after for the next page, or the first item's id as before for the previous page. Use after or before, not both. Emails are kept for 30 days. Needs a full-access key. Read-only.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_emails"
  }
}

Input Schema

NameRequiredDescriptionDefault
afterNoAn email id. Returns emails older than it (the next page).
limitNoNumber of emails to return, 1 to 100. Default 20.
beforeNoAn email id. Returns emails newer than it (the previous page).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds substantial context beyond them: result ordering, body omission, a 30-day retention window, a full-access-key requirement, and the has_more cursor loop. That is exactly the operational behavior an agent needs before calling.

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?

Front-loaded with the endpoint and core behavior, then pagination, retention, and auth in short declarative sentences. No filler or repetition; every sentence carries information the agent needs.

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 three-optional-param listing tool with no output schema, it covers ordering, payload shape, pagination mechanics, data lifetime, and auth requirements — the remaining unknowns (return field set beyond has_more) are discoverable at call time and not required to invoke correctly.

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 coverage is 100%, so baseline is 3, but the description adds real meaning: it explains the pagination pattern (pass the last item's id as after while has_more is true; symmetric before), and states after and before must not be combined — a constraint the schema itself does not express. It says nothing about limit, which the schema already documents.

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 ("Lists emails sent through the API") plus ordering ("newest first") and a deliberate scope limit ("without html/text bodies"). It explicitly routes body retrieval to the sibling get_email, so the agent can distinguish this from get_email without opening either schema.

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 conditional alternative: use get_email when you need html/text bodies. It also gives a mutual-exclusion rule for after/before. It does not cover other conditions (e.g., retrieving a specific known id vs. browsing), but the core when-to-use guidance is explicit.

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