Skip to main content
Glama

list_subscriptions

Read-only

Lists distinct senders in your mailbox with opt-out options and thread counts, helping you spot newsletters and select targets for bulk unsubscribe.

Instructions

Who keeps writing, how often, and whether you can get off the list — a mailbox slice grouped by SENDER, each row carrying its opt-out options. Contacts nobody: opt-out options come from the List-Unsubscribe header of each sender's newest thread (one metadata fetch per sender, not per thread). optOut is 'one-click' (the unsubscribe tool can perform it), 'link' (a human opens it in a browser), 'mailto' (would need sending, which mailwarden never does), 'none', or 'unknown' when that sender's header fetch failed. oldestDate/newestDate bound what the SAMPLE saw of that sender, not the sender's whole history — a query capped at max reaches back only as far as those threads go, which on a busy mailbox is days. There is deliberately NO precomputed frequency: judge it from threads across that span, with the sampling caveat in view. newestThreadId is what to hand to unsubscribe or bulk_unsubscribe. sendersFound is how many DISTINCT senders the sample held — when it exceeds topN, the list is truncated and raising topN shows more. USE WHEN: 'what am I subscribed to', 'which newsletters flood me', or picking targets before a bulk unsubscribe. DO NOT USE: for a general inbox overview (use triage_digest — it buckets by label and age too), or for one known thread (use list_unsubscribe). SIDE EFFECTS: none.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
maxNo
topNNo
queryNocategory:promotions

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
hasMoreYes
sampledYes
sendersFoundYes
subscriptionsYes
Behavior5/5

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

The description goes beyond annotations by detailing optOut types ('one-click', 'link', 'mailto', etc.), explaining the sampling caveat (oldestDate/newestDate bound the sample, not full history), noting no precomputed frequency, and specifying side effects as 'none'. This aligns with readOnlyHint=true and provides context not in structured data.

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?

The description is long but every sentence contributes: it front-loads the core purpose, then systematically covers edge cases, use cases, and side effects. The 'USE WHEN' and 'DO NOT USE' paragraphs provide clear structure without waste.

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

Completeness5/5

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

Given the tool's complexity (sender grouping, opt-out scanning, sampling limits), the description thoroughly covers return value semantics, behavioral caveats, and relationships to sibling tools. It even explains output fields like sendersFound and newestThreadId, making it complete despite having an output schema.

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?

With 0% schema description coverage, the description compensates by explaining what each parameter controls: max caps the query scope, topN truncates the list, and query defines the mailbox slice. It doesn't enumerate parameters directly, but the context adds meaningful semantics beyond raw schema.

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?

The description clearly states the tool lists a mailbox slice grouped by SENDER with opt-out options, which directly conveys a specific verb+resource. It also distinguishes from siblings by mentioning alternatives like triage_digest and list_unsubscribe in the use cases.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit 'USE WHEN' and 'DO NOT USE' sections provide clear guidance: use for subscription understanding or targeting before bulk unsubscribe, avoid for general inbox overview (use triage_digest) or one known thread (use list_unsubscribe). This offers both when and when-not scenarios with named alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/csitte/mailwarden'

If you have feedback or need assistance with the MCP directory API, please join our Discord server