Skip to main content
Glama
debanjanbasu

grr

by debanjanbasu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

tasks.tasklists.insert

Creates a new task list for the authenticated user and adds it to their existing task lists, enabling structured task organization through Google Tasks.

Instructions

Creates a new task list and adds it to the authenticated user's task lists. A user can have up to 2000 lists at a time [HTTP POST] — creates or triggers a change; refused under --readonly safety profiles. Returns the API's response resource as JSON — request body is a JSON TaskList object accepting etag, id, kind, selfLink, title, updated; pass it via params or whole via body_file Siblings over the same resource: delete, get, list, 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. The body is a JSON TaskList object.
request_bodyNoRequest body of type TaskList: pass it via `params` (merged into the built body) or whole via `body_file`.

Output Schema

NameRequiredDescriptionDefault
idNo
etagNo
kindNo
titleNo
updatedNo
selfLinkNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / body_file / description
      Previous value: -"Read the request body from this file ('-' for stdin) instead of building one from the parameters."New value: +"Read the request body from this file ('-' for stdin) instead of building one from the parameters. The body is a JSON TaskList object."
    • addedInput schema / properties / request_body
      Added value: +{
+  "description": "Request body of type TaskList: pass it via `params` (merged into the built body) or whole via `body_file`.",
+  "properties": {
+    "etag": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "selfLink": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "updated": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "etag": {
+      "type": "string"
+    },
+    "id": {
+      "type": "string"
+    },
+    "kind": {
+      "type": "string"
+    },
+    "selfLink": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "updated": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations provided, the description carries the behavioral burden and does a good job: it discloses the 2000-list cap, the HTTP POST mutation semantics, refusal under --readonly safety profiles, and that it returns the API response resource as JSON. It omits auth scope requirements and rate/error behavior, which keeps it off a 5.

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

Conciseness4/5

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

Front-loaded with purpose and quota, then safety, then body format, then sibling routing. Dense and mostly earned, though the trailing list of five sibling names is a bare enumeration that could carry conditions instead.

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 spelled out, yet the description still names the return shape. For a mutation tool with zero annotations and a nested request body, it covers quota, safety gating, and body-passing mechanics well; only permission/scope behavior is unaddressed.

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 the schema already explains params, body_file, query and dry_run; the description largely restates those routes and re-lists the TaskList fields (etag, id, kind, selfLink, title, updated) that the request_body schema already defines. It adds the useful merge note ("pass it via `params` or whole via `body_file`") but little else beyond structured data.

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?

States a specific verb and resource (creates a new task list under the authenticated user) and explicitly enumerates the sibling operations on the same resource (delete, get, list, patch, update). An agent can tell it apart from tasks.tasklists.patch/update without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The create-vs-modify distinction is carried by naming the sibling verbs, which is clear routing context, but no explicit when-not conditions are given (e.g. "use patch to modify an existing list"). The safety-profile refusal note also gives a concrete precondition for calling 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