grr

Overview Schema Source Related Servers Discussions Admin

gmail.users.messages.trash

Move a specified Gmail message to the trash using its user and message IDs, returning the updated resource as JSON. Blocked under read-only safety profiles.

Instructions

Moves the specified message to the trash [HTTP POST] — creates or triggers a change; refused under --readonly safety profiles. Returns the API's response resource as JSON — request bodies are built from the typed parameters (typed flags win over the params map), or read whole from body_file Siblings over the same resource: batchDelete, batchModify, delete, get, import, insert, list, modify, send, untrash.

Input Schema

Name	Required	Description	Default
`id`	Yes	[URL path segment] The ID of the message to Trash.
`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.

Output Schema

Name	Required	Description	Default
`id`	No
`raw`	No
`payload`	No
`snippet`	No
`labelIds`	No
`threadId`	No
`historyId`	No
`internalDate`	No
`sizeEstimate`	No
`classificationLabelValues`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 26, 2026

changedInput schema / properties / id / description

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

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": {
+    "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": {
+                "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"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "raw": {
+      "type": "string"
+    },
+    "sizeEstimate": {
+      "type": "integer"
+    },
+    "snippet": {
+      "type": "string"
+    },
+    "threadId": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A3.6/5.0

Behavior4/5

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

With no annotations, the description carries the safety burden itself and does well: it discloses that this creates/triggers a change and is refused under --readonly safety profiles, and it explains how the request body is assembled (typed flags beat `params`, or `body_file`). It omits what happens when the message is already trashed and whether the action is reversible.

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

Conciseness3/5

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

Purpose is front-loaded, but the body-construction clause is dense and largely restates schema descriptions, and the trailing enumeration of ten siblings is noise that doesn't help select this tool.

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?

An output schema exists, so return-value explanation isn't needed, and the description covers the mutation and safety-profile behavior for a 6-parameter write tool. Remaining gaps (already-trashed behavior, reversibility, required scopes) are modest rather than disqualifying.

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 every parameter is already documented, including the `me` default for userId and the `params` merge precedence. The description adds no parameter detail beyond what the schema already states, so the baseline 3 applies.

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+resource: 'Moves the specified message to the trash', which an agent can distinguish from delete/untrash by name. It stops short of explicitly contrasting the semantics with gmail.users.messages.delete or batchDelete, so the differentiation is inferred rather than stated.

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 name and the sibling list imply this is the reversible removal option versus delete, but the description never says when to pick trash over delete, batchDelete, or modify. The readonly-profile note is environmental context, not usage guidance.

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

Deploy Server