grr

Overview Schema Source Related Servers Discussions Admin

gmail.users.drafts.update

Replace an existing Gmail draft's content with updated message data so you can revise emails before sending.

Instructions

Replaces a draft's content. For more information, see Create and send draft emails [HTTP PUT] — updates the resource; 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: create, delete, get, list, send.

Input Schema

Name	Required	Description	Default
`id`	Yes	[URL path segment] The ID of the draft to update.
`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"
+}

Changed4 schema fields changedOct 26, 2026

changedInput schema / properties / id / description

Previous value: -"The ID of the draft to update."New value: +"[URL path segment] The ID of the draft to update."

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?

With no annotations, the description carries the full burden and discloses important behavior: the operation is HTTP PUT and replaces draft content, it is refused under --readonly safety profiles, and it returns the API response resource as JSON. It does not cover required scopes or error behavior, but the safety-profile refusal is a meaningful disclosure.

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 purpose and efficiently packs in HTTP method, safety behavior, return format, body handling, and sibling context. It is slightly dense but does not waste space.

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 no annotations, a rich input schema, and an output schema, the description covers the key behavioral context: mutation semantics, safety-profile refusal, return format, and body-passing mechanism. It could say more about permissions or usage exclusions, but it is largely complete for calling the tool correctly.

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%, so the schema already documents all parameters thoroughly. The description adds only a brief note that the request body is a Draft object accepting id and message and can be passed via params or body_file, which largely repeats schema-provided information.

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: 'Replaces a draft's content.' It also lists the sibling operations over the same resource (create, delete, get, list, send), making it easy to distinguish this tool from alternatives.

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?

Usage is implied by 'Replaces a draft's content,' which suggests this tool is for modifying an existing draft. The sibling list provides context, but there is no explicit guidance on when to choose update versus send, create, or other alternatives.

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

Deploy Server