Skip to main content
Glama
debanjanbasu

grr

by debanjanbasu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

tasks.tasklists.list

Fetch all task lists belonging to the authenticated user, using pageToken and maxResults to page through results so you can inspect available lists.

Instructions

Returns all the authenticated user's task lists. A user can have up to 2000 lists 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: delete, get, insert, patch, update.

Input Schema

NameRequiredDescriptionDefault
queryNoExtra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
paramsNoParameter map merged into the request; typed parameters win.
dry_runNoReturn the request that would be sent, without sending it.
body_fileNoRead the request body from this file ('-' for stdin) instead of building one from the parameters.
pageTokenNo[query parameter] Token specifying the result page to return. Optional.
maxResultsNo[query parameter] Maximum number of task lists returned on one page. Optional. The default is 1000 (max allowed: 1000).

Output Schema

NameRequiredDescriptionDefault
etagNo
kindNo
itemsNo
nextPageTokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum number of task lists returned on one page. Optional. The default is 1000 (max allowed: 1000)."New value: +"[query parameter] Maximum number of task lists returned on one page. Optional. The default is 1000 (max allowed: 1000)."
    • 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."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "etag": {
+      "type": "string"
+    },
+    "items": {
+      "items": {
+        "properties": {
+          "etag": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "kind": {
+            "type": "string"
+          },
+          "selfLink": {
+            "type": "string"
+          },
+          "title": {
+            "type": "string"
+          },
+          "updated": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "nextPageToken": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, and the description does disclose useful behavior: HTTP GET, JSON responses, and a 2000-list limit. However, it omits pagination behavior despite having pageToken/maxResults parameters, and the boilerplate about request bodies and body_file is irrelevant and potentially confusing for a GET endpoint.

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?

The purpose and 2000-list limit are front-loaded effectively. However, the middle sentence about request bodies is generic boilerplate that does not apply to a GET list operation and dilutes the otherwise compact description.

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?

An output schema exists, so return values need not be explained, and the input schema fully documents the pagination parameters. The description covers scope, HTTP method, and the list cap, leaving only minor gaps such as explicit pagination guidance.

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 the schema already documents all six parameters, including pageToken and maxResults. The description only mentions generic request-construction mechanics (typed parameters overriding the params map, body_file) and adds no specific meaning for the list parameters.

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?

The description states a specific verb and resource: 'Returns all the authenticated user's task lists,' and adds the 2000-list cap. It also names the sibling operations over the same resource (delete, get, insert, patch, update), so an agent can distinguish this list operation from them without opening another schema.

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?

The description names sibling operations but gives no conditions for choosing list over get or any other alternative, and no when-not guidance. The only implied usage is the bare fact that it returns all task lists.

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