Skip to main content
Glama

Hail Communication for AI

List emails

list_emails
Read-onlyIdempotent

List workspace email summaries, newest first.

    Summaries contain IDs and metadata, without message bodies.
    Returns ``items`` and ``next_cursor``, or an error.

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
limitNoHow many items one page holds. ``next_cursor`` in the response points to the next page.
cursorNoPagination cursor: the ``next_cursor`` from the previous page. Omitted: the first page.
statusNoOnly emails currently in this status; ``received`` means inbound. Omitted: every status.
directionNoOnly mail received by the workspace (``inbound``) or only mail it sent (``outbound``). Omitted: both.
llm_modelNoModel ID of the calling agent. Optional. Recorded for analytics only.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Number of items per page."New value: +"How many items one page holds. ``next_cursor`` in the response points to the next page."
    • addedInput schema / properties / llm_model
      Added value: +{
      +  "description": "Model ID of the calling agent. Optional. Recorded for analytics only.",
      +  "type": "string"
      +}
  2. Changed7 schema fields changed
    • changedInput schema / properties / direction / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "outbound",
      +      "inbound"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / direction / description
      Previous value: -"Only ``inbound`` or only ``outbound`` emails."New value: +"Only mail received by the workspace (``inbound``) or only mail it sent (``outbound``). Omitted: both."
    • changedInput schema / properties / limit / description
      Previous value: -"Page size, 1 to 200."New value: +"Number of items per page."
    • addedInput schema / properties / limit / maximum
      Added value: +200
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / status / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "queued",
      +      "sent",
      +      "delivered",
      +      "failed",
      +      "bounced",
      +      "complained",
      +      "received"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • changedInput schema / properties / status / description
      Previous value: -"Only emails in this status: queued, sent, failed, bounced, complained or received."New value: +"Only emails currently in this status; ``received`` means inbound. Omitted: every status."
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is covered. The description adds value the annotations do not: default ordering (newest first), the fact that bodies are omitted, and the 'items'/'next_cursor' or error response shape. It stops short of stating auth requirements, maximum page size behavior, or whether results reflect all statuses by default.

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?

Three short sentences, front-loaded with the core action and scope, followed by the content limitation and the return shape. No filler and nothing repeated from the title or schema.

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

Completeness4/5

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

Given full schema coverage, rich annotations, and an output schema, the description covers the essentials an agent needs: scope, ordering, body exclusion, and pagination return. The only gap is the lack of explicit routing guidance relative to sibling email-reading tools.

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 100%, with limit, cursor, status, and direction all documented in the schema, so the schema carries the semantic load. The description adds nothing about any parameter (no default page size, no filter interaction notes). Baseline 3 applies.

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 ('List workspace email summaries') plus scope (workspace), ordering ('newest first'), and content shape ('IDs and metadata, without message bodies'). The body-exclusion clause implicitly separates it from get_email / get_email_raw without needing to name them.

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 the 'list' verb and the summaries-only note; there is no explicit statement of when to reach for this versus get_email, get_email_raw, or get_email_events. Adequate for an obvious list endpoint, but no exclusions or prerequisites are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources