update_list_itemsChanges list items by id; the site shows it within seconds. On form replies and bookings: only the owner's own columns (not undoable).
| Name | Required | Description | Default |
|---|---|---|---|
| list | Yes | ||
| site | Yes | ||
| items | Yes | Given fields change; null clears. {id, values, if_updated_at; internal: was} |
| Name | Required | Description | Default |
|---|---|---|---|
| items | No | ||
| change_id | No | ||
| agent_message | No |
Changes observed during successful MCP inspections.
Input schema / properties / items / descriptionPrevious value: -"Given fields change; null clears. {id, values, if_updated_at}"New value: +"Given fields change; null clears. {id, values, if_updated_at; internal: was}"Input schema / properties / list / descriptionRemoved value: -"List name"Input schema / properties / site / descriptionRemoved value: -"Site name"Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "agent_message": {
+ "type": "string"
+ },
+ "change_id": {
+ "type": "string"
+ },
+ "items": {
+ "items": {
+ "properties": {
+ "id": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "type": "object"
+}Input schema / properties / items / descriptionPrevious value: -"Given fields change; null clears"New value: +"Given fields change; null clears. {id, values, if_updated_at}"Input schema / properties / items / items / properties / if_updated_atRemoved value: -{
- "type": "string"
-}Input schema / properties / items / items / properties / values / additionalPropertiesRemoved value: -{}Input schema / properties / items / maxItemsRemoved value: -500Input schema / properties / items / minItemsRemoved value: -1Input schema / properties / site / descriptionPrevious value: -"Site name, e.g. brave-otter-4821"New value: +"Site name"Output schema / (root)Previous value: -{
- "additionalProperties": {},
- "properties": {
- "agent_message": {
- "type": "string"
- },
- "confirm_token": {
- "type": "string"
- },
- "error": {
- "description": "On failure (isError): {code, message}"
- }
- },
- "type": "object"
-}New value: +nullDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and idempotency=false, but the description adds useful context: changes propagate in seconds and form-reply/booking updates are limited to owner columns and are not undoable. It does not fully explain broader destructive behavior or permissions, but it meaningfully supplements the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is compact and front-loaded, moving from core behavior to propagation and restrictions without filler. Every clause adds information relevant to invoking the tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema available and annotations covering safety, the description supplies the key behavioral notes: propagation timing and restrictions for form replies/bookings. It could say more about site/list parameters or general undo behavior, but it is mostly complete for this mutation tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is only 33%, and the description adds little parameter detail beyond 'by id'. It does not explain the 'site' or 'list' parameters and only partially clarifies the items payload, leaving the low schema coverage uncompensated.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: 'Changes list items by id'. It is clearly distinct from siblings like add_list_items, remove_list_items, and sort_list_items, though it does not explicitly name an alternative.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied by 'Changes list items by id' and the note about form replies and bookings. However, it gives no explicit when-to-use guidance versus siblings such as update_app_rows or undo_list_change.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.