Skip to main content
Glama

Deliveries Emails Show

deliveries_emails_show

Retrieve details for a specific email delivery using its organisation ID and email ID, with optional query parameters to control included fields.

Instructions

Get details of an email. GET /organisations/{organisationId}/deliveries/emails/{emailId}

query keys (include, fields[...]) pass through verbatim.

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": {
      "organisation_id": "<organisation_id>",
      "email_id": "<email_id>"
    },
    "name": "deliveries_emails_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
email_idYes
organisation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose that ``query`` keys are passed through verbatim without transformation, which is real behavioral context. However, it says nothing about auth/permission requirements, error behavior for an unknown email_id, or what 'details' actually includes.

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?

Very short and front-loaded: the purpose sentence comes first, followed by the endpoint mapping and the query passthrough note. Every line adds something, though the raw HTTP path is somewhat redundant with the parameter names.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read tool with no output schema and no annotations, the description covers the invocation mechanics but not the result: it never indicates what fields a 'detail' response contains or how sparse it is by default without ``include``. An agent can call it, but cannot anticipate the payload.

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 description coverage is 0%, so the description must compensate. It partially does: the path template maps organisation_id and email_id to their positions, and it explains that ``query`` accepts include and fields[...] keys verbatim. It gives no format hints for the IDs and no enumeration of valid ``include`` values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: 'Get details of an email', and the embedded endpoint path confirms it fetches a single delivery email by ID, which distinguishes it from deliveries_emails_list, _events, _cancel, and _delete. It stops short of naming any sibling explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of when to prefer deliveries_emails_events or _file instead, and no stated prerequisites. The agent must infer from the resource name alone that this is the single-record read path.

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