Skip to main content
Glama
gmail-mcp-server

gmail-mcp-server

by fbassas

create_draft

Create a Gmail email draft with recipient, subject, and body details without sending it, so you can review and edit before delivery.

Instructions

Crea un esborrany de correu a Gmail. Aquesta eina mai envia correus.

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": "create_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
bodyYes
subjectYes
threadIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full load, and it does make one genuinely valuable disclosure: the operation never sends mail, which is the primary risk an agent might fear from a 'create' tool. It omits other behavioral facts such as where the draft lands, whether it is editable/deletable afterwards, what permissions are needed, and what happens when threadId is supplied.

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, no filler, with the resource and the critical never-sends guarantee front-loaded. Nothing in the text could be removed without losing information.

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?

For a 4-parameter mutation tool with zero annotation coverage, zero schema descriptions, and no output schema, two sentences are too thin. An agent gets no guidance on the optional threadId, no indication of what the call returns (e.g., a draft identifier), and no failure conditions.

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%, so the description must compensate, and it does not: 'to', 'subject' and 'body' are only loosely inferable from 'correu' (email), while 'threadId' — the least obvious parameter, controlling whether the draft attaches to an existing conversation — is never mentioned. It adds domain framing but no real parameter meaning.

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?

States a specific verb and resource in Catalan: 'Crea un esborrany de correu a Gmail' (creates an email draft in Gmail), which no sibling (list_labels, read_email, search_emails) also does. It stops short of naming how it differs from any sibling tool, so it is clear but not fully 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?

'Aquesta eina mai envia correus' (this tool never sends emails) is a useful boundary that tells the agent to use it for composing rather than dispatch, but no alternative tool or when-not-to-use condition is named. Usage is therefore implied rather than instructed.

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