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

Google Workspace (GWS) MCP Server

tasks_tasks_update

Idempotent

Update a Google Task by changing only specified fields, such as marking it completed by setting status to "completed".

Instructions

Update a task (only supplied fields change). Common use: complete a task by setting status to "completed".

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>",
      "task": "<task>"
    },
    "name": "tasks_tasks_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
dueNoDue date (RFC 3339)
taskYesTask ID to update
notesNoFree-text notes / body
titleNoTask title
statusNoTask status: needsAction or completed
tasklistYesTask list ID

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

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

Annotations already declare readOnly=false, destructive=false, idempotent=true, and openWorld=true. The description adds one meaningful behavioral fact beyond that: unspecified fields are left unchanged, which tells the agent this is a partial update and safe to call idempotently. It says nothing about failure modes, permission requirements, or whether clearing a field is possible.

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, no filler, with the mutation semantics front-loaded and the common use case following. Nothing could be removed without losing information.

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 six-parameter mutation tool with full schema coverage and no output schema, the description covers what it does and the primary use case. It is thin on dependencies between the required tasklist and task parameters and on what the call returns, leaving the agent to infer these.

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 coverage is 100%, so every parameter including the status value set is already documented, giving a baseline of 3. The description reinforces the status parameter with a concrete 'completed' example but adds no format or constraint detail 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?

States a specific verb and resource ('Update a task') and clarifies the patch semantics in parentheses ('only supplied fields change'), which an agent can act on directly. It does not explicitly contrast with siblings like tasks_tasks_insert or tasks_tasks_move, but the verb/resource pairing is distinct enough to select it.

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?

Gives one concrete usage pattern ('complete a task by setting status to "completed"'), which is genuinely helpful for the most common case. It offers no when-not guidance, no mention of related operations such as tasks_tasks_move for reordering, and no prerequisites (e.g., needing the tasklist ID).

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