move_emailsMove messages to a folder other than the archive or trash.
| Name | Required | Description | Default |
|---|---|---|---|
| folder | Yes | Destination folder name or role | |
| accountId | No | Account to operate on. Optional when exactly one account is connected. | |
| messageIds | Yes | Messages to change, up to 100 IDs |
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": false,
+ "properties": {
+ "data": {
+ "additionalProperties": true,
+ "properties": {
+ "action": {
+ "type": "string"
+ },
+ "failed": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "code": {
+ "type": "string"
+ },
+ "messageId": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "messageId",
+ "code"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "succeededIds": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "uncertainIds": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "action",
+ "succeededIds",
+ "failed",
+ "uncertainIds"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "data"
+ ],
+ "type": "object"
+}Input schema / properties / accountId / anyOfPrevious value: -[
- {
- "minLength": 1,
- "type": "string"
- },
- {
- "type": "null"
- }
-]New value: +[
+ {
+ "maxLength": 512,
+ "minLength": 1,
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / folder / maxLengthAdded value: +512Input schema / properties / messageIds / descriptionPrevious value: -"Messages to change, up to 100 distinct IDs"New value: +"Messages to change, up to 100 IDs"Input schema / properties / messageIds / items / maxLengthAdded value: +512Input schema / properties / messageIds / maxItemsAdded value: +100Input schema / $schemaPrevious value: -"https://json-schema.org/draft/2020-12/schema"New value: +"http://json-schema.org/draft-07/schema#"Input schema / properties / accountId / anyOfAdded value: +[
+ {
+ "minLength": 1,
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / accountId / descriptionAdded value: +"Account to operate on. Optional when exactly one account is connected."Input schema / properties / accountId / maxLengthRemoved value: -512Input schema / properties / accountId / minLengthRemoved value: -1Input schema / properties / accountId / typeRemoved value: -"string"Input schema / properties / folder / descriptionAdded value: +"Destination folder name or role"Input schema / properties / folder / maxLengthRemoved value: -512Input schema / properties / messageIds / descriptionAdded value: +"Messages to change, up to 100 distinct IDs"Input schema / properties / messageIds / items / maxLengthRemoved value: -512Input schema / properties / messageIds / maxItemsRemoved value: -100Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already disclose that the operation mutates data, is destructive, and is idempotent, so the description carries less burden. It adds the useful destination constraint excluding archive/trash, but does not explain permissions, folder existence requirements, or side effects beyond what annotations already state.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The definition is a single front-loaded sentence with no wasted text. The core action and the key destination restriction are both stated immediately.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With complete schema descriptions, rich annotations, and an output schema, the short description is nearly sufficient for correct invocation. The main remaining gap is not explicitly naming archive_emails and trash_emails as the alternatives for excluded destinations.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so messageIds, folder, and accountId are already fully documented in the schema. The description adds no parameter-level meaning beyond the schema, which is acceptable at the baseline for complete schemas.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: moving messages to a folder. It also distinguishes this tool from archive_emails and trash_emails by excluding the archive and trash destinations, though it does not explicitly name those sibling tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'other than the archive or trash' gives an implied when-not constraint, routing archive/trash actions to other tools. However, it does not explicitly name the alternatives or explain when moving to a custom folder is preferred over other organization tools like add_labels.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.