Skip to main content
Glama
m-ishit

gmail-mcp-server

by m-ishit

Send an email (irreversible)

send_email
Destructive

Sends a real email after explicit user confirmation of recipients, subject, and body. Requires confirmed consent to avoid accidental sending.

Instructions

⚠️ IRREVERSIBLE: Sends a real email immediately on behalf of the user — there is no undo, no "are you sure" prompt from Gmail, and no draft-review step once this is called. Only call this tool after the human user has explicitly and unambiguously confirmed the exact recipient(s), subject, and body of THIS specific email in the current conversation. If there is any ambiguity about content, recipients, or intent — or if you have not shown the user the exact text you're about to send — use create_draft instead and ask the user to review and send it themselves. Never call this proactively, as part of a speculative multi-step plan, or based on inferred rather than explicitly stated intent.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ccNo
toYes
bccNo
accountYesThe Gmail address to operate on. Must be one of the accounts returned by list_accounts. If you don't know which account to use, call list_accounts first and ask the user if ambiguous.
subjectYes
bodyHtmlNoOptional HTML body, sent alongside the plain-text body.
bodyTextYesPlain-text body.
threadIdNoSet to send as a reply within an existing thread.
confirmedYesMust be exactly `true`. Set this only after the human user has explicitly confirmed the recipients, subject, and body of this exact email in the current conversation.
Behavior5/5

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

Adds rich context beyond the destructiveHint annotation: irreversible, no undo, no draft-review step, requirement for confirmed field. Explains the exact behavior and consequences.

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 paragraph front-loaded with a strong warning. Every sentence adds value: purpose, usage guidance, behavioral warning, when-not, alternative. No wasted 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?

Given the tool's complexity (irreversible, 9 parameters, 56% schema coverage, no output schema), the description covers essential behavioral and usage context. Could mention success/failure behavior but still adequate.

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 description coverage is 56%. The description emphasizes the critical 'confirmed' parameter and account prerequisite, but does not add much per-parameter detail beyond what the schema already provides.

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?

Clearly states it sends a real email immediately on behalf of the user. Distinguishes from sibling 'create_draft' by specifying when to use the alternative.

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?

Explicitly provides when to use (after explicit user confirmation) and when not (ambiguity, speculative planning, inferred intent). Names alternative tool 'create_draft'.

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/m-ishit/gmail-mcp-server'

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