Skip to main content
Glama

List customer emails

list_customer_emails
Read-onlyIdempotent

Lists the customer emails in one store's connected mailbox, 20 per page: to answer (answer), sorted for a person (needs_you) or sent. Each row has the subject, the sender's name and masked address, the topic, the status and whether a draft is ready. Needs the conversations permission and the store's switch for AI assistants in Settings > Security, and works only for stores the person owns.

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": {
      "store_id": "<store_id>"
    },
    "name": "list_customer_emails"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabNoanswer
pageNo
topicNo
periodNoThe days covered, by when the conversation or email arrived.30d
searchNo
store_idYesThe store's store_id (not its name).

Output Schema

NameRequiredDescriptionDefault
toNo
tabNo
fromNo
moreNo
pageNo
countsYes
emailsYes
store_idYes
dashboard_urlNo
mailbox_connectedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations (which already cover read-only, idempotent, closed-world) by disclosing fixed page size of 20, the exact fields in each row including masked sender addresses, and the authorization gates: permission scope, a per-store feature switch, and owner-only access. Those are the failure modes an agent needs to know 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the resource and page size before the tab semantics and prerequisites. Dense and mostly waste-free, though the row-field enumeration is arguably redundant with the output 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 six parameters, low schema coverage, and an existing output schema, the description covers the operation, the mode selection, pagination, row shape, and all access prerequisites. The remaining gap is per-parameter semantics for topic, search, and page.

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 only 33%, so the description must compensate. It does explain the highest-value gap, the tab enum values, but says nothing about topic, search, page, or period beyond what the schema already provides, leaving several parameters with no added meaning.

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 with scope: 'Lists the customer emails in one store's connected mailbox, 20 per page'. It also defines the three tab modes, which distinguishes it functionally from list_conversations, though it never names that sibling to make the boundary explicit.

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?

Explains what each tab is for ('to answer', 'sorted for a person', 'sent'), which tells an agent which mode to pick for a given intent, and states the prerequisites (conversations permission, AI-assistant switch in Settings > Security, owner-only stores). No explicit when-not-to-use or named alternative tool, so short of a 5.

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