Skip to main content
Glama

Deliveries Emails List

deliveries_emails_list

Retrieve a paginated list of email deliveries for an organisation, with sorting, filtering, and custom query parameters to find and review sent emails.

Instructions

Get a collection of emails. GET /organisations/{organisationId}/deliveries/emails

Extra query parameters (sort, filter, q, include, fields[...]) pass through verbatim via query; page_number/page_limit map to page[number]/page[limit].

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>"
    },
    "name": "deliveries_emails_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNo
page_limitNo
page_numberNo
organisation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It discloses that this is a GET/list operation, that extra query parameters pass through verbatim, and how page_number/page_limit map to page[number]/page[limit]. It omits auth requirements, default or maximum page size, and response shape, which are significant for an unannotated tool.

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?

The description is front-loaded with the verb, resource, and endpoint, then adds only the necessary parameter mapping notes. Backticks and line breaks add slight noise but no sentence is wasted.

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?

Given no annotations and no output schema, the description provides useful endpoint and pagination context but leaves key operational details unspecified: authentication/permissions, pagination defaults, and the shape of the returned collection. For a list endpoint in a large sibling family, this is only partially complete.

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 0%, so the description must explain all four parameters. It covers query (sort, filter, q, include, fields) and the page_number/page_limit mapping well, but organisation_id is only implied by the endpoint rather than explained. Overall this is strong compensation for the schema gap.

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 and resource ('Get a collection of emails') and gives the exact endpoint, which lets an agent distinguish it from email show/create/cancel siblings. It does not explicitly contrast with sibling list tools such as deliveries_ebills_list, but the resource name and collection scope are clear.

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 by saying it returns a collection; there is no explicit guidance on when to use this instead of deliveries_emails_show or other list endpoints, nor any stated prerequisites. That is adequate minimum context but leaves clear gaps.

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