grr

Overview Schema Source Related Servers Discussions Admin

tasks.tasks.list

List tasks in a specified Google Tasks list, with optional filters for due/completion dates, pagination, and hidden, deleted, or assigned tasks.

Instructions

Returns all tasks in the specified task list. Doesn't return assigned tasks by default (from Docs, Chat Spaces). A user can have up to 20,000 non-hidden tasks per list and up to 100,000 tasks in total at a time [HTTP GET]. Returns the requested resource as JSON — request bodies are built from the typed parameters (typed flags win over the params map), or read whole from body_file Siblings over the same resource: clear, delete, get, insert, move, patch, update.

Input Schema

Name	Required	Description
`query`	No	Extra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
`dueMax`	No	[query parameter] Upper bound for a task's due date (as a RFC 3339 timestamp) to filter by. Optional. The default is not to filter by due date.
`dueMin`	No	[query parameter] Lower bound for a task's due date (as a RFC 3339 timestamp) to filter by. Optional. The default is not to filter by due date.
`params`	No	Parameter map merged into the request; typed parameters win.
`dry_run`	No	Return the request that would be sent, without sending it.
`tasklist`	Yes	[URL path segment] Task list identifier.
`body_file`	No	Read the request body from this file ('-' for stdin) instead of building one from the parameters.
`pageToken`	No	[query parameter] Token specifying the result page to return. Optional.
`maxResults`	No	[query parameter] Maximum number of tasks returned on one page. Optional. The default is 20 (max allowed: 100).
`showHidden`	No	[query parameter] Flag indicating whether hidden tasks are returned in the result. Optional. The default is False.
`updatedMin`	No	[query parameter] Lower bound for a task's last modification time (as a RFC 3339 timestamp) to filter by. Optional. The default is not to filter by last modification time.
`showDeleted`	No	[query parameter] Flag indicating whether deleted tasks are returned in the result. Optional. The default is False.
`completedMax`	No	[query parameter] Upper bound for a task's completion date (as a RFC 3339 timestamp) to filter by. Optional. The default is not to filter by completion date.
`completedMin`	No	[query parameter] Lower bound for a task's completion date (as a RFC 3339 timestamp) to filter by. Optional. The default is not to filter by completion date.
`showAssigned`	No	[query parameter] Optional. Flag indicating whether tasks assigned to the current user are returned in the result. Optional. The default is False.
`showCompleted`	No	[query parameter] Flag indicating whether completed tasks are returned in the result. Note that showHidden must also be True to show tasks completed in first party clients, such

Output Schema

Name	Required	Description	Default
`etag`	No
`kind`	No
`items`	No
`nextPageToken`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedOct 26, 2026

changedInput schema / properties / completedMax / description

Previous value: -"Upper bound for a task's completion date (as a RFC 3339 timestamp) to filter by. Optional. The default is not to filter by completion date."New value: +"[query parameter] Upper bound for a task's completion date (as a RFC 3339 timestamp) to filter by. Optional. The default is not to filter by completion date."

changedInput schema / properties / completedMin / description

Previous value: -"Lower bound for a task's completion date (as a RFC 3339 timestamp) to filter by. Optional. The default is not to filter by completion date."New value: +"[query parameter] Lower bound for a task's completion date (as a RFC 3339 timestamp) to filter by. Optional. The default is not to filter by completion date."

changedInput schema / properties / dueMax / description

Previous value: -"Upper bound for a task's due date (as a RFC 3339 timestamp) to filter by. Optional. The default is not to filter by due date."New value: +"[query parameter] Upper bound for a task's due date (as a RFC 3339 timestamp) to filter by. Optional. The default is not to filter by due date."

changedInput schema / properties / dueMin / description

Previous value: -"Lower bound for a task's due date (as a RFC 3339 timestamp) to filter by. Optional. The default is not to filter by due date."New value: +"[query parameter] Lower bound for a task's due date (as a RFC 3339 timestamp) to filter by. Optional. The default is not to filter by due date."

changedInput schema / properties / maxResults / description

Previous value: -"Maximum number of tasks returned on one page. Optional. The default is 20 (max allowed: 100)."New value: +"[query parameter] Maximum number of tasks returned on one page. Optional. The default is 20 (max allowed: 100)."

addedInput schema / properties / maxResults / format
```
Added value: +"int32"
```

changedInput schema / properties / pageToken / description

Previous value: -"Token specifying the result page to return. Optional."New value: +"[query parameter] Token specifying the result page to return. Optional."

changedInput schema / properties / showAssigned / description

Previous value: -"Optional. Flag indicating whether tasks assigned to the current user are returned in the result. Optional. The default is False."New value: +"[query parameter] Optional. Flag indicating whether tasks assigned to the current user are returned in the result. Optional. The default is False."

changedInput schema / properties / showCompleted / description

Previous value: -"Flag indicating whether completed tasks are returned in the result. Note that showHidden must also be True to show tasks completed in first party clients, such "New value: +"[query parameter] Flag indicating whether completed tasks are returned in the result. Note that showHidden must also be True to show tasks completed in first party clients, such "

changedInput schema / properties / showDeleted / description

Previous value: -"Flag indicating whether deleted tasks are returned in the result. Optional. The default is False."New value: +"[query parameter] Flag indicating whether deleted tasks are returned in the result. Optional. The default is False."

changedInput schema / properties / showHidden / description

Previous value: -"Flag indicating whether hidden tasks are returned in the result. Optional. The default is False."New value: +"[query parameter] Flag indicating whether hidden tasks are returned in the result. Optional. The default is False."

changedInput schema / properties / tasklist / description

Previous value: -"Task list identifier."New value: +"[URL path segment] Task list identifier."

changedInput schema / properties / updatedMin / description

Previous value: -"Lower bound for a task's last modification time (as a RFC 3339 timestamp) to filter by. Optional. The default is not to filter by last modification time."New value: +"[query parameter] Lower bound for a task's last modification time (as a RFC 3339 timestamp) to filter by. Optional. The default is not to filter by last modification time."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "etag": {
+      "type": "string"
+    },
+    "items": {
+      "items": {
+        "properties": {
+          "assignmentInfo": {
+            "properties": {
+              "driveResourceInfo": {
+                "properties": {
+                  "driveFileId": {
+                    "type": "string"
+                  },
+                  "resourceKey": {
+                    "type": "string"
+                  }
+                },
+                "type": "object"
+              },
+              "linkToTask": {
+                "type": "string"
+              },
+              "spaceInfo": {
+                "properties": {
+                  "space": {
+                    "type": "string"
+                  }
+                },
+                "type": "object"
+              },
+              "surfaceType": {
+                "enum": [
+                  "CONTEXT_TYPE_UNSPECIFIED",
+                  "GMAIL",
+                  "DOCUMENT",
+                  "SPACE"
+                ],
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "completed": {
+            "type": "string"
+          },
+          "deleted": {
+            "type": "boolean"
+          },
+          "due": {
+            "type": "string"
+          },
+          "etag": {
+            "type": "string"
+          },
+          "hidden": {
+            "type": "boolean"
+          },
+          "id": {
+            "type": "string"
+          },
+          "kind": {
+            "type": "string"
+          },
+          "links": {
+            "items": {
+              "properties": {
+                "description": {
+                  "type": "string"
+                },
+                "link": {
+                  "type": "string"
+                },
+                "type": {
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "notes": {
+            "type": "string"
+          },
+          "parent": {
+            "type": "string"
+          },
+          "position": {
+            "type": "string"
+          },
+          "selfLink": {
+            "type": "string"
+          },
+          "status": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "updated": {
+            "type": "string"
+          },
+          "webViewLink": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "nextPageToken": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

B3.4/5.0

Behavior4/5

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

No annotations are provided, so the description must carry behavioral disclosure. It supplies useful context: HTTP GET, default exclusion of assigned tasks, quota limits (20,000 per list / 100,000 total), JSON return format, and request-body handling via typed parameters or body_file.

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

Conciseness3/5

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

Purpose and key defaults are front-loaded, but the description includes generic wrapper boilerplate about JSON return and body_file that is largely irrelevant for a GET list operation. The bare sibling list also adds length without routing guidance.

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?

Given the fully described schema and an output schema, the description covers the essentials an agent needs: purpose, default exclusion behavior, quotas, HTTP method, and request/response handling. It does not cover auth or rate limits, but those are less critical for selecting this listing tool.

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 all 16 parameters are already documented in the schema. The description adds only general wrapper semantics and the default assigned-task behavior, not parameter-specific guidance beyond what the schema provides, so the baseline 3 applies.

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: 'Returns all tasks in the specified task list,' and notes the default exclusion of assigned tasks. It names sibling operations over the same resource but does not explain how they differ, so it stops short of full sibling differentiation.

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 explicit when-to-use or when-not-to-use guidance. The default-exclusion note gives context, but the agent is not told when to choose this over tasks.tasks.get, tasks.tasks.insert, or other sibling operations.

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

Deploy Server