Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

gmail_send_draft

Send an existing Gmail draft by its draft ID so prepared email content can be dispatched without recreating or re-entering it.

Instructions

Send an existing draft.

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

Input Schema

NameRequiredDescriptionDefault
draftIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation profile is covered, but the description adds nothing beyond them. It does not mention that the send is externally visible (openWorldHint), that the draft is removed from Drafts after sending, or that the action cannot be undone. For an outbound-send tool, that silence is a real gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence, front-loaded with the action and free of filler. It is efficient, though the brevity is closer to under-specification than disciplined concision.

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?

The tool is simple (one required string, no output schema), so a short description is defensible, but it omits what happens on success or failure and how to source the draftId. Even for a low-complexity tool, the agent lacks enough to call it correctly without trial and error.

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?

With one parameter at 0% schema description coverage, the description carries the full burden and mostly fails: 'draftId' is never explained, nor is where the agent obtains a valid ID (e.g. from gmail_list_drafts or gmail_create_draft's response). Only the word 'existing' hints at the value's origin.

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 states a specific verb and resource ('Send' + 'draft') and the qualifier 'existing' implicitly separates it from gmail_create_draft and gmail_send. It does not, however, explicitly name the sibling it differs from, so an agent must infer the boundary.

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?

There is only implied guidance: 'existing draft' tells the agent a draftId must already exist before calling, which rules out fresh composition. It names no alternatives and gives no preconditions (e.g. that the draft is consumed or moved to Sent), so the routing decision is left to inference.

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