Skip to main content
Glama
Google Workspace (GWS) MCP Server

Google Workspace (GWS) MCP Server

tasks_tasklists_delete

DestructiveIdempotent

Deletes a task list and removes any assigned task originals from Google Docs or Chat Spaces.

Instructions

Delete a task list. If it contains assigned tasks, the originals (in Docs/Chat Spaces) are also removed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tasklist": "<tasklist>"
    },
    "name": "tasks_tasklists_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
tasklistYesTask list ID to delete

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Addedv0.4.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, so the safety profile is known. The description adds genuinely non-obvious behavior beyond that: deletion cascades to originals in Docs/Chat Spaces when assigned tasks exist. It omits whether unassigned tasks are simply discarded and whether any confirmation or permission scope is required.

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

Conciseness5/5

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

Two short sentences: the action first, then the consequence. No filler, no repetition of the title, and the warning is placed where a scanning agent will see it.

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?

For a single-parameter destructive tool with no output schema, the description covers the essential risk (cascading removal of originals). The remaining gap is whether tasks in the list without external originals are also destroyed, which an agent would reasonably want before invoking.

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?

Only one parameter and the schema already documents it fully ('Task list ID to delete'), so description coverage is redundant territory. The description adds no format, source, or lookup guidance for obtaining the ID, 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?

Specific verb ('Delete') plus specific resource ('a task list'), which cleanly separates it from tasks_tasks_delete (deletes a task) and tasks_tasklists_update. It stops short of explicitly naming siblings or stating what the tool is not, so it lands at 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no prerequisite or permission note, and no mention of alternatives such as clearing tasks instead of deleting the list. The conditional sentence covers a side effect of calling it, not when calling it is appropriate.

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