Skip to main content
Glama

gmail send email

gmail_send_email

Sends an email with To/Cc/Bcc and HTML support; requires explicit confirmation and permission, otherwise returns a dry-run preview for safe review.

Instructions

Send an email. Requires confirm=true and allow_email_send=true; returns a dry-run preview otherwise.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "to": "<to>",
      "subject": "<subject>",
      "body": "<body>"
    },
    "name": "gmail_send_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNo
toYes
bccNo
bodyYes
htmlNo
confirmNo
dry_runNo
subjectYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

The annotations only declare the generic safety profile (readOnlyHint=false, openWorldHint=true, destructiveHint=false, idempotentHint=false). The description adds something the annotations cannot convey: the tool silently degrades to a dry-run preview unless two specific flags are set, which is exactly the kind of non-obvious behavior an agent must know before calling. It could go further by noting irreversibility, rate limits, or what the preview looks like, but the core hidden behavior is disclosed.

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?

Two sentences, no filler, and the action statement plus the gating condition are both front-loaded. Every clause carries information an agent needs.

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?

The output schema exists, so return-value shape need not be explained, and the send-safety gate is covered. But for an 8-parameter, open-world, non-idempotent write tool with zero schema descriptions, the definition leaves too much unstated — particularly dry_run versus confirm precedence and the recipient/formatting parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 8 parameters, so the description carries the full explanatory burden and mostly does not meet it. It discusses only confirm and allow_email_send, and the latter is not even an input parameter here; cc, bcc, html, dry_run, and the interaction between dry_run and the confirm gate are left completely undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: "Send an email." That is unambiguous and distinguishes it from the draft-creation sibling by implication. It stops short of explicitly naming gmail_create_draft as the non-sending alternative, so it is clear but not maximally differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a real precondition (confirm=true plus allow_email_send=true) and states what happens when that precondition is unmet, which is useful usage guidance. However, it never says when to send versus when to save a draft, nor does it mention that an actual send is irreversible and cannot be recalled, leaving the key routing decision to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.