Skip to main content
Glama

Coline

Search mail

search_mail
Read-onlyIdempotent

Finds mail threads by sender, subject, topic or words in them.

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": {
      "workspace": "<workspace>",
      "query": "<query>"
    },
    "name": "search_mail"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
cursorNonextCursor from the previous page, with the same filters.
accountIdNoMail account id from list_mailboxes or a thread.
workspaceYesWorkspace slug from workspaces.list, e.g. "acme".

Output Schema

NameRequiredDescriptionDefault
threadsYes
nextCursorYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive, so the safety profile is fully covered. The description contributes only the matching scope (sender, subject, topic, body words); it says nothing about pagination, result ordering, or the limit cap, which is the behavior an agent most needs to reason about for a paged search.

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?

A single front-loaded sentence with the verb first and zero filler. It is efficiently written, though its brevity leaves little structural room for the paging or scoping clauses the tool would benefit from.

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?

With an output schema present and annotations covering safety, the description need not explain return values. However, for a 5-parameter paged search with two required scoping inputs, it omits the default limit, the cursor-based continuation behavior, and any note that results are repo-free keyword matches rather than exhaustive listings.

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?

At 60% schema coverage, the schema documents workspace, accountId, and cursor but leaves query and limit bare. The description compensates partly by explaining what the query string matches against (sender, subject, topic, words), which is real added meaning, but it never mentions limit, paging via cursor, or how account scoping affects results.

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?

"Finds mail threads by sender, subject, topic or words in them" gives a specific verb (finds) plus resource (mail threads) and the matching dimensions, which separates it from read-style siblings like read_mail_thread or show_mail. It stops short of explicitly contrasting itself with list_mail_threads, so an agent must infer the search-vs-enumerate distinction from the name alone.

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 or when-not-to-use guidance and no named alternative. An agent with list_mail_threads, search_messages, and search available gets no signal about which to pick for a keyword lookup versus a full listing.

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