Skip to main content
Glama
Cresca MCP Server

Cresca MCP Server

Retrieve email

get_email
Read-onlyIdempotent

Retrieve a sent email by ID to inspect its recipients, subject, content, tags, and latest delivery status. Use it to verify whether an email was queued, sent, delivered, bounced, or failed.

Instructions

GET /emails/:id. Returns one email sent through the API: from, to, cc, bcc, reply_to, subject, html, text, created_at, scheduled_at, tags and its latest status as last_event (queued, scheduled, sending, sent, delivered, delivery_delayed, bounced, complained, failed, suppressed or canceled). "delivered" means the receiving server accepted it, not that it reached the inbox. Emails are kept for 30 days. Needs a full-access key. Read-only.

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": {
      "id": "<id>"
    },
    "name": "get_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe email id returned when it was sent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent and open-world, but the description adds real operational context: a full-access key is required, records expire after 30 days, and the status vocabulary is spelled out with the important caveat that 'delivered' does not mean inbox placement. That last note materially changes how an agent should interpret results.

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 endpoint and the core behavior, then the return fields, then caveats. The long status enumeration is justified because the semantics matter, though the field list is slightly dense and could be trimmed given it duplicates the response payload.

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?

With no output schema, the description carries the full burden of describing the return value and does so comprehensively, including the status enum, retention window, and auth requirement. Nothing an agent needs to call or interpret this tool is missing.

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

Parameters3/5

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

Schema coverage is 100% and the single id parameter is documented in-schema, so no compensation is needed. The description adds only the endpoint path form ':id', which does not extend meaning beyond the schema; baseline 3 is appropriate.

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 ('Returns one email sent through the API') plus the endpoint, and enumerates the returned fields. The singular 'one email' implicitly separates it from list_emails and search-style siblings, so an agent can place it without opening the schema.

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

Usage Guidelines3/5

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

Usage is only implied: fetching a single email by id requires the id from a prior send, and the full-access key prerequisite is noted. There is no explicit when-to-use versus list_emails or get_template guidance, and no exclusion conditions, which keeps this at minimum-viable.

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