Skip to main content
Glama
Sign In
MCP Google Multi-Account Server

MCP Google Multi-Account Server

by bkbaheti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

gmail_send_draft

Sends a draft email from a specified Google account after confirmation. Requires account ID, draft ID, and explicit confirmation to prevent accidental sends.

Instructions

Send a draft email. IMPORTANT: This will actually send the email. You MUST pass confirm: true to proceed. Requires compose or full scope.

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": {
      "accountId": "<accountId>",
      "draftId": "<draftId>",
      "confirm": "<confirm>"
    },
    "name": "gmail_send_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesREQUIRED: Must be true to actually send. This is a safety gate to prevent accidental sends.
draftIdYesThe draft ID to send
accountIdYesThe Google account ID, alias, or email

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.3

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It explicitly warns 'This will actually send the email' and emphasizes the confirm safety gate, which is crucial for an irreversible action. It also mentions the required OAuth scope. It does not describe post-send behavior, but the key risks are covered.

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?

The description is two sentences long, front-loaded with the core purpose, and includes a critical safety warning. Every sentence provides value, and there is no fluff or repetition.

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?

For a simple send action, the description covers the essential context: the irreversible nature, the confirmation requirement, and the required scope. It does not explain return values, but no output schema is present and the action's outcome is obvious. Sibling tools provide enough surrounding context to distinguish this operation.

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% and each parameter has a clear description in the schema. The tool description repeats the confirm requirement but does not add additional meaning beyond what the schema already provides. Baseline 3 applies because the schema does the heavy lifting.

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 states 'Send a draft email' with a specific verb and resource, clearly distinguishing it from sibling tools like gmail_create_draft, gmail_update_draft, and gmail_delete_draft. The action is unambiguous and leaves no doubt about what the tool does.

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?

The description makes clear that this tool is for sending an already-created draft, which is implied by the context. It does not explicitly name alternatives or exclusions, but the contrast with other draft-related tools is evident. The safety warning about confirm being required is an operational guideline.

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