grr

Overview Schema Source Related Servers Discussions Admin

gmail.users.drafts.create

Creates a Gmail draft with the DRAFT label so you can compose or stage an email without sending it. Returns the API response as JSON.

Instructions

Creates a draft with the DRAFT label. For more information, see Create and send draft emails [HTTP POST] — creates or triggers a change; refused under --readonly safety profiles. Returns the API's response resource as JSON — request body is a JSON Draft object accepting id, message; pass it via params or whole via body_file Siblings over the same resource: delete, get, list, send, update.

Input Schema

Name	Required	Description	Default
`query`	No	Extra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
`params`	No	Parameter map merged into the request; typed parameters win.
`userId`	Yes	[URL path segment] The user's email address. The special value `me` can be used to indicate the authenticated user.	me
`dry_run`	No	Return the request that would be sent, without sending it.
`body_file`	No	Read the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON Draft object.
`request_body`	No	Request body of type Draft: pass it via `params` (merged into the built body) or whole via `body_file`.

Output Schema

Name	Required	Description	Default
`id`	No
`message`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

changedInput schema / properties / body_file / description

Previous value: -"Read the request body from this file ('-' for stdin) instead of building one from the parameters."New value: +"Read the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON Draft object."

addedInput schema / properties / request_body

Added value: +{
+  "description": "Request body of type Draft: pass it via `params` (merged into the built body) or whole via `body_file`.",
+  "properties": {
+    "id": {
+      "type": "string"
+    },
+    "message": {
+      "properties": {
+        "classificationLabelValues": {
+          "items": {
+            "properties": {
+              "fields": {
+                "items": {
+                  "properties": {
+                    "fieldId": {
+                      "type": "string"
+                    },
+                    "selection": {
+                      "type": "string"
+                    }
+                  },
+                  "type": "object"
+                },
+                "type": "array"
+              },
+              "labelId": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "historyId": {
+          "type": "string"
+        },
+        "id": {
+          "type": "string"
+        },
+        "internalDate": {
+          "type": "string"
+        },
+        "labelIds": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "payload": {
+          "properties": {
+            "body": {
+              "properties": {
+                "attachmentId": {
+                  "type": "string"
+                },
+                "data": {
+                  "type": "string"
+                },
+                "size": {
+                  "type": "integer"
+                }
+              },
+              "type": "object"
+            },
+            "filename": {
+              "type": "string"
+            },
+            "headers": {
+              "items": {
+                "properties": {
+                  "name": {
+                    "type": "string"
+                  },
+                  "value": {
+                    "type": "string"
+                  }
+                },
+                "type": "object"
+              },
+              "type": "array"
+            },
+            "mimeType": {
+              "type": "string"
+            },
+            "partId": {
+              "type": "string"
+            },
+            "parts": {
+              "items": {
+                "properties": {
+                  "body": {
+                    "type": "object"
+                  },
+                  "filename": {
+                    "type": "string"
+                  },
+                  "headers": {
+                    "items": {
+                      "type": "object"
+                    },
+                    "type": "array"
+                  },
+                  "mimeType": {
+                    "type": "string"
+                  },
+                  "partId": {
+                    "type": "string"
+                  },
+                  "parts": {
+                    "items": {
+                      "type": "object"
+                    },
+                    "type": "array"
+                  }
+                },
+                "type": "object"
+              },
+              "type": "array"
+            }
+          },
+          "type": "object"
+        },
+        "raw": {
+          "type": "string"
+        },
+        "sizeEstimate": {
+          "type": "integer"
+        },
+        "snippet": {
+          "type": "string"
+        },
+        "threadId": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

Changed3 schema fields changedOct 26, 2026

addedInput schema / properties / userId / default
```
Added value: +"me"
```

changedInput schema / properties / userId / description

Previous value: -"The user's email address. The special value `me` can be used to indicate the authenticated user."New value: +"[URL path segment] The user's email address. The special value `me` can be used to indicate the authenticated user."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "id": {
+      "type": "string"
+    },
+    "message": {
+      "properties": {
+        "classificationLabelValues": {
+          "items": {
+            "properties": {
+              "fields": {
+                "items": {
+                  "properties": {
+                    "fieldId": {
+                      "type": "string"
+                    },
+                    "selection": {
+                      "type": "string"
+                    }
+                  },
+                  "type": "object"
+                },
+                "type": "array"
+              },
+              "labelId": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "historyId": {
+          "type": "string"
+        },
+        "id": {
+          "type": "string"
+        },
+        "internalDate": {
+          "type": "string"
+        },
+        "labelIds": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "payload": {
+          "properties": {
+            "body": {
+              "properties": {
+                "attachmentId": {
+                  "type": "string"
+                },
+                "data": {
+                  "type": "string"
+                },
+                "size": {
+                  "type": "integer"
+                }
+              },
+              "type": "object"
+            },
+            "filename": {
+              "type": "string"
+            },
+            "headers": {
+              "items": {
+                "properties": {
+                  "name": {
+                    "type": "string"
+                  },
+                  "value": {
+                    "type": "string"
+                  }
+                },
+                "type": "object"
+              },
+              "type": "array"
+            },
+            "mimeType": {
+              "type": "string"
+            },
+            "partId": {
+              "type": "string"
+            },
+            "parts": {
+              "items": {
+                "properties": {
+                  "body": {
+                    "type": "object"
+                  },
+                  "filename": {
+                    "type": "string"
+                  },
+                  "headers": {
+                    "items": {
+                      "type": "object"
+                    },
+                    "type": "array"
+                  },
+                  "mimeType": {
+                    "type": "string"
+                  },
+                  "partId": {
+                    "type": "string"
+                  },
+                  "parts": {
+                    "items": {
+                      "type": "object"
+                    },
+                    "type": "array"
+                  }
+                },
+                "type": "object"
+              },
+              "type": "array"
+            }
+          },
+          "type": "object"
+        },
+        "raw": {
+          "type": "string"
+        },
+        "sizeEstimate": {
+          "type": "integer"
+        },
+        "snippet": {
+          "type": "string"
+        },
+        "threadId": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A3.9/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that this is a mutating POST, that it creates or triggers a change, that it is refused under `--readonly` profiles, and that it returns the API's response resource as JSON. It leaves out auth scope and rate-limit details, but covers the critical write/safety behavior for this operation.

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?

The description is front-loaded with the core action and stays compact despite covering safety, return format, body handling, and siblings. A few clauses about the request body are redundant with the schema, but the paragraph is still efficient.

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?

Given the moderate complexity, rich schema, and existing output schema, the description supplies the key missing context: mutation behavior, readonly-profile refusal, body-passing alternatives, and sibling operations. It does not cover auth or error handling, but nothing essential for invoking this tool is missing.

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 description coverage is 100%, so the schema already documents parameters thoroughly. The description adds a little body-construction guidance by naming the JSON Draft object, its `id` and `message` fields, and the `params` versus `body_file` alternatives, but that largely repeats schema-level information. Baseline 3 is appropriate when schema coverage is this high.

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 a specific verb and resource: 'Creates a draft with the `DRAFT` label.' It also names the sibling operations over the same resource (delete, get, list, send, update), so an agent can distinguish this create operation from related draft actions without opening the schema.

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?

The description implies usage by naming sibling operations and notes that the HTTP POST is 'refused under --readonly safety profiles,' which is useful context. However, it does not explicitly say when to use this instead of `gmail.users.drafts.send` or how drafts are intended to be used in a workflow.

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

Deploy Server