Skip to main content
Glama
Sign In
Gmail MCP

Gmail MCP

by shinzo-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

verify_send_as

Send a verification email to confirm a send-as alias. Validate custom email addresses for use in Gmail.

Instructions

Sends a verification email to the specified send-as alias

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": {
      "sendAsEmail": "<sendAsEmail>"
    },
    "name": "verify_send_as"
  }
}

Input Schema

NameRequiredDescriptionDefault
sendAsEmailYesThe send-as alias to be verified

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It only states the action, omitting side effects (e.g., email sent to alias owner), required state (alias must be unverified), or outcome (e.g., user must follow link). Minimal transparency.

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?

One concise sentence with no wasted words. Information is front-loaded and easy to parse.

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

Completeness2/5

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

Lacks critical context: no mention of return value, error states (e.g., alias already verified), or required user steps. Despite simplicity of the action, the description is incomplete for an agent to understand full implications.

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?

The single parameter sendAsEmail is described in the schema as 'The send-as alias to be verified.' The description does not add extra meaning or format details beyond the schema. With 100% schema coverage, 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 ('Sends a verification email') and the target resource ('to the specified send-as alias'). It uniquely identifies the tool's purpose among siblings like create_send_as or get_send_as, which focus on other operations.

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?

No explicit guidance on when to use this tool versus alternatives. The description implies usage when verification is needed, but lacks context such as prerequisites (alias existence, unverified status) or comparative notes with other tools.

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

Deploy Server

Other Tools