Skip to main content
Glama
Sign In
google-workspace-mcp

google-workspace-mcp

by smk-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

task_delete

Permanently delete a Google Task from a specified account and task list by task ID. Use to remove unwanted tasks; deletion cannot be undone.

Instructions

Delete a task. Irreversible.

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": {
      "account": "<account>",
      "task_id": "<task_id>"
    },
    "name": "task_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountYes
task_idYes
tasklist_idNo@default

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.2

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only states 'Irreversible', which is important, but omits other key aspects such as permissions required, effects on subtasks, or whether deletion requires ownership. The single trait is insufficient for a destructive operation.

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?

The description is very concise (two sentences) with no redundant words. However, it lacks structure and is too minimal for a 3-parameter tool. It is not well-structured to guide an agent on usage.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 3 parameters (two required), no output schema, and no annotations, the description is severely incomplete. It fails to explain the role of each parameter, the context of the task (e.g., which task list), or the return value. The agent cannot reliably invoke this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 0%, so the description must compensate. However, it provides no explanation of the three parameters (account, task_id, tasklist_id). The agent cannot infer the format or purpose of account or task_id beyond their names.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Delete a task' clearly states the verb (delete) and resource (a task). It is unambiguous and distinguishes from sibling tools like task_complete (which marks complete) and task_update (which modifies).

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?

The description mentions 'Irreversible' as a caution, but does not provide explicit guidance on when to use this tool versus alternatives like task_complete or task_update. No conditions or prerequisites are given.

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

Deploy Server

Other Tools