haus

update_task

Update a task's title, assignee, due date, reminders, notes or urgency. Only the fields you send change.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Task id from create_task or list_tasks.
`notes`	No	Freeform notes. Not for assignment info.
`title`	No	New title.
`dueDate`	No	New due date, YYYY-MM-DD. Empty string clears it.
`isUrgent`	No	Mark the task urgent so it is shown first and highlighted: true marks urgent, false clears it, omit to leave unchanged.
`preparationDate`	No	Legacy single reminder date, YYYY-MM-DD; use reminderOffsetMinutes instead. Ignored when reminderOffsetMinutes is sent. Must be on or before dueDate. Empty string clears it; clearing dueDate clears it. On a task without reminderOffsetMinutes, changing dueDate does not move it. On a task with reminderOffsetMinutes the server keeps it in step with dueDate: a different date replaces every reminder with that one, and an empty string removes them all.
`assignedToMemberId`	No	Member id to assign. Empty string unassigns.
`reminderOffsetMinutes`	No	New reminder lead times, in minutes before the due date. Send the full list: it replaces the current one. [] clears all reminders; omit to keep them. Each value is whole hours, 60-1380 (1-23 hours), or whole days, a multiple of 1440 up to 525600 (365 days); a week is 10080. Up to 5 values. A due date counts from 00:00 on that day, so 300 (5 hours) is 19:00 the evening before. Day and week reminders arrive at 19:00 on the earlier day; hour reminders arrive that many hours before, or up to 15 minutes earlier. Reminders move with dueDate, need a due date, and are cleared when dueDate is cleared.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes
`title`	No
`message`	No
`variant`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 24, 2026

addedInput schema / properties / isUrgent

Added value: +{
+  "description": "Mark the task urgent so it is shown first and highlighted: true marks urgent, false clears it, omit to leave unchanged.",
+  "examples": [
+    true
+  ],
+  "type": "boolean"
+}

changedInput schema / properties / preparationDate / description

Previous value: -"New preparation date, YYYY-MM-DD. Must not follow dueDate. Empty string clears it."New value: +"Legacy single reminder date, YYYY-MM-DD; use reminderOffsetMinutes instead. Ignored when reminderOffsetMinutes is sent. Must be on or before dueDate. Empty string clears it; clearing dueDate clears it. On a task without reminderOffsetMinutes, changing dueDate does not move it. On a task with reminderOffsetMinutes the server keeps it in step with dueDate: a different date replaces every reminder with that one, and an empty string removes them all."

addedInput schema / properties / reminderOffsetMinutes

Added value: +{
+  "description": "New reminder lead times, in minutes before the due date. Send the full list: it replaces the current one. [] clears all reminders; omit to keep them. Each value is whole hours, 60-1380 (1-23 hours), or whole days, a multiple of 1440 up to 525600 (365 days); a week is 10080. Up to 5 values. A due date counts from 00:00 on that day, so 300 (5 hours) is 19:00 the evening before. Day and week reminders arrive at 19:00 on the earlier day; hour reminders arrive that many hours before, or up to 15 minutes earlier. Reminders move with dueDate, need a due date, and are cleared when dueDate is cleared.",
+  "examples": [
+    [
+      1440,
+      10080
+    ]
+  ],
+  "items": {
+    "description": "One lead time in minutes: whole hours 60-1380, or a multiple of 1440 for days.",
+    "examples": [
+      1440
+    ],
+    "maximum": 525600,
+    "minimum": 60,
+    "multipleOf": 60,
+    "type": "integer"
+  },
+  "maxItems": 5,
+  "type": "array",
+  "uniqueItems": true
+}

Changed8 schema fields changedSep 8, 2026

changedInput schema / properties / assignedToMemberId / description

Previous value: -"Member ID to assign, or empty string to unassign. Omit to leave the current assignment unchanged."New value: +"Member id to assign. Empty string unassigns."

changedInput schema / properties / dueDate / description

Previous value: -"YYYY-MM-DD format, or empty string to clear. Omit to leave unchanged."New value: +"New due date, YYYY-MM-DD. Empty string clears it."

changedInput schema / properties / id / description

Previous value: -"The task's ID, as returned by create_task or list_tasks."New value: +"Task id from create_task or list_tasks."

changedInput schema / properties / notes / description

Previous value: -"Freeform notes about the task. Not for assignment info. Omit to leave unchanged."New value: +"Freeform notes. Not for assignment info."

addedInput schema / properties / notes / examples
```
Added value: +[
+  "Blue bin only"
+]
```

changedInput schema / properties / preparationDate / description

Previous value: -"YYYY-MM-DD format, or empty string to clear. Omit to leave unchanged."New value: +"New preparation date, YYYY-MM-DD. Must not follow dueDate. Empty string clears it."

changedInput schema / properties / title / description

Previous value: -"New title for the task. Omit to leave unchanged; max 200 characters."New value: +"New title."

addedInput schema / properties / title / examples

Added value: +[
+  "Take out the recycling"
+]

Changed11 schema fields changedJul 14, 2026

addedInput schema / examples

Added value: +[
+  {
+    "dueDate": "2026-08-01",
+    "id": "018f2c9a1b2c7d3e9a4f5b6c7d8e9f0a",
+    "title": "Take out the recycling"
+  }
+]

changedInput schema / properties / assignedToMemberId / description

Previous value: -"Member ID to assign, or empty string to unassign"New value: +"Member ID to assign, or empty string to unassign. Omit to leave the current assignment unchanged."

addedInput schema / properties / assignedToMemberId / examples
```
Added value: +[
+  "7f3a9c2e1b4d8f6a0c5e3b7d9a1f4c6e"
+]
```

changedInput schema / properties / dueDate / description

Previous value: -"YYYY-MM-DD format, or empty string to clear"New value: +"YYYY-MM-DD format, or empty string to clear. Omit to leave unchanged."

addedInput schema / properties / dueDate / examples
```
Added value: +[
+  "2026-08-01"
+]
```

addedInput schema / properties / id / description

Added value: +"The task's ID, as returned by create_task or list_tasks."

addedInput schema / properties / id / examples

Added value: +[
+  "018f2c9a1b2c7d3e9a4f5b6c7d8e9f0a"
+]

changedInput schema / properties / notes / description

Previous value: -"Freeform notes about the task. Not for assignment info."New value: +"Freeform notes about the task. Not for assignment info. Omit to leave unchanged."

changedInput schema / properties / preparationDate / description

Previous value: -"YYYY-MM-DD format, or empty string to clear"New value: +"YYYY-MM-DD format, or empty string to clear. Omit to leave unchanged."

addedInput schema / properties / preparationDate / examples
```
Added value: +[
+  "2026-07-30"
+]
```

addedInput schema / properties / title / description

Added value: +"New title for the task. Omit to leave unchanged; max 200 characters."

Changed2 schema fields changedJul 3, 2026

changedInput schema / properties / dueDate / description

Previous value: -"YYYY-MM-DD format"New value: +"YYYY-MM-DD format, or empty string to clear"

changedInput schema / properties / preparationDate / description

Previous value: -"YYYY-MM-DD format"New value: +"YYYY-MM-DD format, or empty string to clear"

First observedJun 30, 2026

TDQS

A3.6/5.0

Behavior4/5

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

The description adds an important behavioral guarantee beyond annotations: 'Only the fields you send change,' clearly signaling partial-update semantics. Annotations only say the operation is neither read-only nor destructive, so this extra context is valuable and non-contradictory.

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

Conciseness5/5

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

The description is a single, efficient sentence that front-loads the essential action and immediately communicates the key partial-update behavior. There is no filler or redundant restatement of the tool name.

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 rich input schema and presence of an output schema, the description covers the critical caller-facing behavior: only sent fields change. It lacks sibling routing and some operational warnings, but for this tool's complexity it is generally sufficient.

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%, and the schema already provides detailed meaning for every parameter. The description's field list roughly maps to the parameters but adds no new detail beyond what the schema supplies, so the baseline of 3 is appropriate.

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 clearly states the verb and resource ('Update a task') and enumerates the fields involved, making the tool's purpose immediately obvious. It does not explicitly contrast itself with siblings like assign_task or update_recurring_task, so it falls short of full 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?

The description provides no guidance on when to use this tool versus alternatives such as assign_task, complete_task, or create_task. It implies use on an existing task, but it does not state exclusions or preferred alternatives for overlapping operations.

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

All haus tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?