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

google-tasks-mcp

by justerlex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

update_task

Update a task's title, notes, due date, or completion status. Requires task list and task IDs.

Instructions

Update a task's title, notes, due date, or status (needsAction | 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": "update_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
dueNoNew due date, YYYY-MM-DD (or full RFC3339)
taskYesTask id
notesNoNew notes
titleNoNew title
statusNoNew status
tasklistYesTask list id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. Only states 'Update' without disclosing side effects, auth needs, partial update behavior, or idempotency. Insufficient for a mutation tool.

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?

Single sentence, front-loaded with purpose. No filler or redundant content.

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?

Adequate for a simple update tool with 6 parameters (2 required). Schema covers params, but description could mention that other fields remain unchanged or the response. No output schema leaves a gap.

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%, so baseline is 3. Description adds no extra meaning beyond schema; it merely lists some parameters already documented.

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?

Clear verb ('Update') and resource ('a task'), explicitly lists updatable fields (title, notes, due date, or status) with allowed status values. Distinguishes from sibling tools like complete_task.

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?

No explicit guidance on when to use vs. alternatives (e.g., complete_task, create_task). Implies use for modifying listed fields but does not mention when not to use it.

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