Skip to main content
Glama

Count email conversations

count_conversations
Read-only

Use this when the user asks how many email conversations there are, such as how many are unread. Returns the number of email conversations in each folder (inbox, sent, unread, favorite, archived, spam and trash), for every mailbox or the ones named. Email only. Free.

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": "count_conversations"
  }
}

Input Schema

NameRequiredDescriptionDefault
foldersNoThe folders to count, separated by commas: `inbox`, `sent`, `unread`, `favorite`, `archived`, `spam`, `trash`. All of them when left out.
mailboxNoOnly these mailboxes: one address, or up to 20 separated by commas.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.3/5.0
Behavior4/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. The description adds value annotations cannot: the operation is free and is limited to email, plus it enumerates which folders are counted 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 triggering condition, then the return shape, then the scope and cost qualifiers. No filler and nothing buried.

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?

There is no output schema, but the description explains precisely what comes back (a count per folder per mailbox), and annotations carry the safety profile. For a two-optional-parameter read-only count, nothing an agent needs is missing.

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 100% and both parameters are fully documented in the schema, including the comma-separated folder enum and the 20-mailbox limit. The description only restates the default ('for every mailbox or the ones named'), so it adds little beyond the schema; 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 ('count email conversations') and describes the exact return shape: counts per folder (inbox, sent, unread, favorite, archived, spam, trash) across all or named mailboxes. The 'Email only' qualifier separates it from count_companies and count_people without needing to open any schema.

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?

'Use this when the user asks how many email conversations there are, such as how many are unread' gives a concrete triggering condition. It does not name a when-not case or point to list_conversations as the alternative when the user wants the actual messages rather than a count, which keeps it 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