grr

Overview Schema Source Related Servers Discussions Admin

tasks.tasks.update

Update a specified task via HTTP PUT with a JSON Task body, modifying fields such as title, due date, completion, and assignment info; returns the API response as JSON.

Instructions

Updates the specified task [HTTP PUT] — updates the resource; refused under --readonly safety profiles. Returns the API's response resource as JSON — request body is a JSON Task object accepting assignmentInfo, completed, deleted, due, etag, hidden, id, kind and 9 more fields; pass it via params or whole via body_file Siblings over the same resource: clear, delete, get, insert, list, move, patch.

Input Schema

Name	Required	Description
`task`	Yes	[URL path segment] Task identifier.
`query`	No	Extra KEY=VALUE query pairs for endpoints whose parameters Discovery does not describe.
`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. The body is a JSON Task object.
`request_body`	No	Request body of type Task: pass it via `params` (merged into the built body) or whole via `body_file`.

Output Schema

Name	Required	Description	Default
`id`	No
`due`	No
`etag`	No
`kind`	No
`links`	No
`notes`	No
`title`	No
`hidden`	No
`parent`	No
`status`	No
`deleted`	No
`updated`	No
`position`	No
`selfLink`	No
`completed`	No
`webViewLink`	No
`assignmentInfo`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 26, 2026

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 Task object."

addedInput schema / properties / request_body

Added value: +{
+  "description": "Request body of type Task: pass it via `params` (merged into the built body) or whole via `body_file`.",
+  "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"
+}

Changed3 schema fields changedOct 26, 2026

changedInput schema / properties / task / description

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

changedInput schema / properties / tasklist / description

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

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "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"
+}

First observedOct 26, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It discloses HTTP PUT, readonly-profile refusal, and JSON response behavior, but it does not explain replacement semantics, required permissions, or what happens to fields omitted from the Task body.

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?

The purpose and key HTTP/safety facts are front-loaded, and most of the text earns its place. The long em-dash/semicolon sentence and trailing sibling list make it denser than ideal, but it remains efficient overall.

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?

Given seven parameters, no annotations, and a rich schema, the description covers call mechanics and return behavior adequately. It still omits the update-versus-patch selection rule and the consequences of PUT-style replacement, which are important for a mutating operation.

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 baseline is 3. The description restates the body field mechanism and routing via params or body_file, but adds little beyond the schema and uses the vague phrase 'and 9 more fields' rather than clarifying semantics.

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?

The description names a specific verb and resource: it 'Updates the specified task' and identifies the HTTP method as PUT. It also mentions the return value and sibling operations, but it does not explain how update differs from patch, so it falls 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 Guidelines3/5

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

It gives a when-not signal by stating the call is refused under --readonly safety profiles and lists sibling operations over the same resource. However, it provides no explicit rule for choosing update versus patch, move, or the other siblings, so usage is only implied.

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

Deploy Server