Skip to main content
Glama
neutral-Stage

Gmail MCP Server

mark_spam

Mark one or more Gmail messages as spam using their message IDs, moving them to the Spam folder. This action helps manage unwanted emails.

Instructions

Mark one or more emails as spam (moves to Spam folder).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesGmail message ID(s) to mark as spam
Behavior2/5

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

The description mentions the effect (moves to Spam folder) but fails to disclose any other behavioral traits such as whether it affects spam training, if it's reversible, or any authorization requirements. With no annotations, this is insufficient.

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?

Single sentence, no wasted words. Front-loaded with the core action and effect.

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

Completeness3/5

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

Adequate for a simple tool with one parameter, but lacks usage guidelines and deeper behavioral context. The description is incomplete when considering sibling tools that perform similar actions.

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% with the 'ids' parameter already described well. The description adds no additional semantic meaning beyond what's in the schema, so baseline 3 is appropriate.

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 action (mark as spam) and the resource (emails), and adds the detail that it moves to the Spam folder. This distinguishes it from sibling tools like batch_trash_emails.

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?

No explicit guidance on when to use this tool vs alternatives like trash or modify. The description does not provide any when-to-use or when-not-to-use context.

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/neutral-Stage/gmail-mcp-server'

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