tasks_delete_list
Deletes a specific Google Tasks list by its ID, removing the list and all its tasks.
Instructions
Delete a Google Task list
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| taskListId | Yes | ID of the task list to delete |
Deletes a specific Google Tasks list by its ID, removing the list and all its tasks.
Delete a Google Task list
| Name | Required | Description | Default |
|---|---|---|---|
| taskListId | Yes | ID of the task list to delete |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Only says 'Delete' without disclosing irreversibility, side effects (e.g., tasks inside deleted), or permissions needed.
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, no wasted words. Efficient, but could benefit from slightly more detail without becoming verbose.
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?
For a simple delete operation with one parameter, the description is minimally adequate. However, it lacks context such as irreversibility or effect on child tasks, which users need.
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 100%, and the description adds no extra meaning beyond what the schema already provides for taskListId. Baseline score of 3 is appropriate.
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?
Description clearly states the action (delete) and resource (Google Task list), distinguishing it from siblings like tasks_delete (which likely deletes a single task) and tasks_create_list.
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 like tasks_delete. No mention of prerequisites, when not to use, or exclusions.
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/salviz/google-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server