untrash_message
Recover a deleted email from the trash folder and restore it to your inbox.
Instructions
Restore a message from Trash.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| message_id | Yes | ||
| account | No | ||
| password | No |
Recover a deleted email from the trash folder and restore it to your inbox.
Restore a message from Trash.
| Name | Required | Description | Default |
|---|---|---|---|
| message_id | Yes | ||
| account | No | ||
| password | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description does not disclose behavioral traits like authentication needs, side effects, or error conditions. Barely adds value beyond the tool name.
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?
Single sentence is concise but lacks necessary detail. It earns its place but could be improved with additional context.
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?
Given 3 parameters, no output schema, and no annotations, the description is severely incomplete. It fails to explain authentication parameters or the result of the operation.
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 coverage is 0%, and description adds no meaning to parameters like 'account' and 'password'. The required 'message_id' is self-explanatory but not explained.
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 verb 'Restore' and resource 'message from Trash' clearly defines the action. It distinguishes from sibling 'untrash_thread' by specifying 'message'.
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?
No guidance on when to use this tool vs alternatives. No mention of prerequisites (e.g., message must be in trash) or exclusion cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/eitan3/Gmail_MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server