Skip to main content
Glama
Sign In
your-mail-mcp

your-mail-mcp

by wildsurfer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Go
Hybrid

ids

Read-only

Returns message IDs matching a notmuch query (from:, subject:, date:) across one or all IMAP accounts, optionally including junk and trash folders.

Instructions

Return the message ids matching a query.

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

Input Schema

NameRequiredDescriptionDefault
queryYesnotmuch query, for example from:alice@example.com and date:2026-01-01..2026-06-30. Terms: from: to: subject: tag: folder: attachment: date:, combined with and/or/not. A bare word matches anywhere in the message.
accountNoLimit the search to one account, named as folders and status report it. Omit to search every account at once.
include_excludedNoSet true to also search the junk and trash folders, which are left out by default. Use it only when a message is expected to be there, since mail in those folders is more likely to be hostile.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.5.0
    • addedInput schema / properties / account / description
      Added value: +"Limit the search to one account, named as folders and status report it. Omit to search every account at once."
    • addedInput schema / properties / include_excluded / description
      Added value: +"Set true to also search the junk and trash folders, which are left out by default. Use it only when a message is expected to be there, since mail in those folders is more likely to be hostile."
    • addedInput schema / properties / query / description
      Added value: +"notmuch query, for example from:alice@example.com and date:2026-01-01..2026-06-30. Terms: from: to: subject: tag: folder: attachment: date:, combined with and/or/not. A bare word matches anywhere in the message."
  2. First observedv0.3.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds nothing beyond the annotations — no note on ordering of results, whether ids are notmuch message ids, or that default search excludes junk/trash (deferred to the schema).

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 sentence with zero filler, front-loading the result type. Its brevity verges on under-specification rather than wordiness, so it is efficient but not exemplary.

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

Completeness2/5

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

For a tool whose output is a bare list of ids meant to be chained into other tools, the description omits result ordering, whether ids are stable/unique, and how they relate to the show/thread siblings. No output schema exists, so the description should carry more of this burden.

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% and the schema documents the notmuch query syntax, account scoping, and the include_excluded caveat in detail. The description names only 'query', so it neither adds nor detracts from what the schema already provides — baseline 3.

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 result ('Return the message ids') scoped to 'matching a query', which tells an agent this yields identifiers rather than full messages. It does not differentiate from siblings like search or count, which is the only thing missing for a 5.

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 statement of when to prefer this over search, count, or show, and no hint that the returned ids are the natural input to show/thread. The only implied usage is that a query is required.

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

Deploy Server

Other Tools