Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

gmail_create_draft

Creates an unsent Gmail draft with recipients, subject, body, and optional attachments from local files or Google Drive IDs.

Instructions

Create an email draft (not sent). Supports attachments.

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": {
      "subject": "<subject>",
      "body": "<body>"
    },
    "name": "gmail_create_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNo
toNo
bccNo
bodyYes
htmlNo
subjectYes
driveFileIdsNoDrive file IDs/URLs to attach. Google Docs/Slides are attached as PDF, Sheets as XLSX.
attachmentPathsNoAbsolute local file paths to attach

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds the useful non-obvious fact that the draft is not sent and that attachments are supported, but doesn't say whether the draft appears in the Drafts folder or how attachment failures behave.

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 short sentences, front-loaded with the core action and the critical 'not sent' qualifier. No wasted wording.

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?

With 8 parameters, 25% schema coverage, no output schema and no annotations explaining return shape, the definition leaves too much unsaid — notably the distinction between the two attachment parameters and what the created draft's identifier looks like. For a mutation tool of this size it should do more.

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 only 25% — only driveFileIds and attachmentPaths are documented, while to, cc, bcc, body, subject and html are bare. The description's 'Supports attachments' gestures at attachment capability but does not clarify the two distinct attachment mechanisms (Drive IDs vs local absolute paths) or the html body flag, so it fails to compensate for the coverage gap.

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?

Clear verb+resource: 'Create an email draft' with the parenthetical '(not sent)' confirming it persists rather than delivers. That distinguishes it from gmail_send/gmail_send_draft, though it never names those siblings explicitly.

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?

'(not sent)' implies the draft-vs-send decision but no explicit guidance is given about when to draft instead of sending, nor any prerequisite or scope notes. An agent can infer the use case but must reason about alternatives itself.

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