Skip to main content
Glama

Update a list

update_list
DestructiveIdempotent

Use this when the user wants to rename a list, move it into a folder, or take it out of its folder. Name the folder by id, or by name, which creates the folder when the list's kind has none; send folderId as null to take the list out of every folder. A folder holds one kind of list. Free.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "listId": "<listId>"
    },
    "name": "update_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoA new name.
listIdYesThe list's id.
folderIdNoMove the list into this folder, one for the list's own kind, or out of every folder with null.
folderNameNoMove the list into the folder of this name, in any case, which is created when the list's kind has none. Send this or `folderId`, not both.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=false, so the safety bar is lower; the description still adds non-obvious behavior: naming a folder by name creates it when the list's kind has none, passing folderId as null removes the list from all folders, a folder holds only one kind of list, and the call is "Free." It does not explain what happens on a name collision or an unknown listId, which a mutation tool could usefully state.

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?

Three sentences, front-loaded with the usage trigger, followed by the parameter mechanics and then constraints. Every sentence carries information; the trailing fragment "Free." is terse to the point of being slightly ambiguous about whether it means cost or a free-text field.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 4-parameter mutation tool with full annotation coverage and no output schema, the description covers triggering, the two folder-targeting modes, the removal case, the kind constraint, and cost. An agent has everything required to construct a correct call without opening the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3, but the description adds meaning beyond the schema: it establishes that folderId and folderName are alternative ways to name the same target, that folderName auto-creates the folder, and that the folder must match the list's kind. That is genuine semantic value, especially the kind-matching constraint, which appears nowhere in the parameter descriptions.

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 names a specific resource (a list) and enumerates the exact operations: rename, move into a folder, or remove from its folder. An agent can distinguish this from delete_list or create_list purely from the text, and the three supported mutations are spelled out rather than left to the 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?

It opens with an explicit trigger condition ("Use this when the user wants to rename a list, move it into a folder, or take it out of its folder"), which maps directly onto the callable operations. It stops short of naming exclusions or alternatives such as delete_list for removal, so a 4 rather than a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources