Skip to main content
Glama
chandshy
by chandshy

Bulk Star/Unstar Emails

bulk_star
Idempotent

Apply or remove star status on multiple emails using their UIDs. Receive progress notifications and success/failed counts.

Instructions

Star or unstar multiple emails. Emits progress notifications. Returns success/failed counts. Pass sourceFolder whenever the UIDs came from a folder other than INBOX.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailIdsYesArray of email UIDs
isStarredNo
sourceFolderNoFolder the UID(s) live in (e.g. INBOX, Folders/Work, Labels/Foo). Strongly recommended whenever the UIDs came from a folder other than INBOX — IMAP UIDs are folder-scoped, so without this the wrong folder may be selected and the operation may silently no-op. Avoid passing 'All Mail' as the source: it is a union view of every folder, not a real location, so moves out of it can silently do nothing — pass the message's actual folder instead. Moving to the folder a message is already in is a no-op.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successYes
failedYes
errorsYes
Behavior4/5

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

Adds behavior not in annotations: emits progress notifications, returns success/failed counts, and warns about silent no-ops if sourceFolder is wrong. Consistent with idempotentHint=true.

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 concise sentences that front-load the core action and then provide essential context. No unnecessary words.

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

Completeness4/5

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

Covers the key nuance of folder-scoped UIDs and mentions output format (counts). With an output schema, this is sufficiently complete for a bulk operation.

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?

Adds significant meaning beyond the schema for 'sourceFolder', explaining why it's needed (IMAP folder-scoped UIDs) and how to use it correctly. The other parameters are adequately described in the 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 verb 'Star or unstar' and the resource 'multiple emails', distinguishing it from single-email star tools like 'star_email' and other bulk actions like 'bulk_mark_read'.

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?

Explicitly advises to pass 'sourceFolder' when UIDs come from a non-INBOX folder and warns against using 'All Mail', but does not explicitly state when not to use this tool over 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/chandshy/mailpouch'

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