Remove labels from multiple emails at once by specifying email IDs and mailbox IDs to clean up your Fastmail inbox efficiently.
Remove labels from multiple emails simultaneously
| Name | Required | Description | Default |
|---|---|---|---|
| emailIds | Yes | Array of email IDs to remove labels from | |
| mailboxIds | Yes | Array of mailbox IDs to remove as labels |
Changes observed during successful MCP inspections.
v1.8.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description only states the basic operation. It does not disclose behavioral traits such as whether the operation is destructive, reversible, requires permissions, handles partial failures, or has rate limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence. While front-loaded, it is too brief and lacks necessary context, making it merely adequate.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no annotations, no output schema, and the presence of sibling tools, the description is incomplete. It does not explain return values, error handling, how it differs from 'remove_labels', or confirm whether labels are removed from all emails atomically.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage with clear parameter descriptions. The tool description adds no extra meaning beyond what the schema provides, so baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action 'Remove labels', the resource 'labels', and the scope 'from multiple emails simultaneously'. It effectively distinguishes from sibling tools like 'remove_labels' (singular) and 'add_labels' (opposite).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives like 'remove_labels' or 'bulk_remove_'. There is no mention of prerequisites, conditions, or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.