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

Google Workspace (GWS) MCP Server

tasks_tasks_clear

DestructiveIdempotent

Hide all completed tasks in a task list without deleting them, so cleared items stop appearing in default list responses while remaining recoverable.

Instructions

Hide all completed tasks in a list. Cleared tasks are not deleted but stop appearing in default list responses.

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_tasks_clear"
  }
}

Input Schema

NameRequiredDescriptionDefault
tasklistYesTask list ID to clear

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.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds genuinely new context: the hide is non-destructive to the underlying data and only affects default list responses. It does not explain how to reverse the operation (unhide), which keeps it from a 5, but it usefully softens what the destructive flag might otherwise suggest.

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 with zero filler; the core action is front-loaded and the clarifying nuance follows immediately. Nothing is repeated from the title or schema in a wasteful way.

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 one-parameter tool with full schema coverage and annotations carrying the safety profile, the definition covers the essential behavioral nuance (data persists, default views change). The only meaningful omission is reversibility, i.e., how a cleared task becomes visible again.

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?

There is a single required parameter with 100% schema description coverage ("Task list ID to clear"), so the schema already does the documentation work. The description adds no format hints, sourcing notes, or constraints beyond what the schema states, matching the baseline 3 for high-coverage schemas.

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?

"Hide all completed tasks in a list" gives a specific verb (hide) and a specific scope (completed tasks within one list), which an agent can distinguish from the delete siblings. It stops short of naming any sibling explicitly, so differentiation is conveyed by implication rather than routing.

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

Usage Guidelines3/5

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

The phrase "not deleted but stop appearing in default list responses" implicitly tells the agent to prefer this over tasks_tasks_delete when the goal is decluttering rather than removal. However, there is no explicit when-to-use statement and no mention of how this relates to tasks_tasks_update, so the agent must infer the alternative.

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