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

Google Workspace (GWS) MCP Server

tasks_tasklists_update

Idempotent

Update a Google Tasks task list by ID; provide a new title to change it, and fields you omit remain unchanged.

Instructions

Update a task list (only supplied fields change).

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

Input Schema

NameRequiredDescriptionDefault
titleNoNew task list title
tasklistYesTask list ID to update

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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=true, so the safety profile is covered structurally. The parenthetical 'only supplied fields change' adds genuine PATCH-vs-PUT semantics beyond the annotations, but the description says nothing about authorization needs, behavior when the tasklist ID is invalid, or what a successful response contains.

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

Conciseness4/5

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

A single short sentence with zero filler, and the operation is front-loaded. The parenthetical is well-placed, though the definition is terse enough that it provides no structural framing for an agent deciding between siblings.

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

Completeness3/5

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

For a two-parameter mutation tool with full schema coverage and explicit annotations, the essentials are present and there is no output schema to explain. However, mutation-relevant details such as required scopes, error conditions for unknown tasklist IDs, and uniqueness of titles are absent, leaving moderate gaps.

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?

Schema description coverage is 100%, with both 'title' and 'tasklist' documented in the schema, so the baseline is 3. The description reinforces optionality of 'title' through 'only supplied fields change' but adds no format, ID syntax, or constraint details beyond the schema.

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?

The description states a specific verb and resource ('Update a task list'), which is unambiguous about the operation. It does not differentiate itself from sibling tools such as tasks_tasklists_get, tasks_tasklists_delete, or tasks_tasklists_insert, so the agent gets no explicit routing signal beyond the verb.

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 guidance on when to use this tool versus alternatives (e.g., insert for new lists, delete for removal, tasks_tasks_update for items). No prerequisites, permission requirements, or conditions for choosing a partial update are mentioned.

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