google-tasks-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_tasklistsA | List all of the user's task lists (id, title, updated). |
| get_tasklistB | Get a single task list by id. |
| create_tasklistB | Create a new task list. Emoji in titles render fine in the Google Tasks apps. |
| update_tasklistB | Rename a task list. |
| delete_tasklistA | Delete a task list AND all tasks in it. Irreversible: confirm intent before calling. |
| list_tasksA | List tasks in a task list. By default returns only active (needsAction) tasks; set the show* flags for completed/hidden/deleted ones. Note: tasks completed in the Google Tasks apps become hidden, so harvesting completions needs showCompleted AND showHidden. |
| get_taskC | Get a single task by id. |
| create_taskA | Create a task. Due dates are DATE-ONLY in Google Tasks (any time portion is discarded); pass YYYY-MM-DD and it is normalized safely. |
| update_taskA | Update a task's title, notes, due date, or status (needsAction | completed). |
| complete_taskA | Mark a task completed (shorthand for update_task with status=completed). |
| delete_taskC | Delete a single task. |
| move_taskA | Reorder a task (position is read-only; this is the only way to reorder), re-parent it as a subtask, or move it to another list via destinationTasklist. |
| diff_tasksA | Harvest every change since a timestamp: returns tasks updated after |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Each tool targets a distinct resource and action. Even complete_task is clearly described as a shorthand for update_task, so no ambiguity. All tools have clear boundaries.
All tools follow a consistent verb_noun pattern in snake_case (e.g., list_tasklists, create_task, delete_task). No mixing of conventions or inconsistent verb styles.
13 tools is well-scoped for a task management domain, covering CRUD for tasklists and tasks, plus specialized actions like complete, move, and diff. Each tool earns its place.
The tool set provides complete lifecycle coverage: CRUD for tasklists and tasks, marking complete, reordering, subtask creation, and a sync mechanism via diff_tasks. No obvious gaps for the domain.