Skip to main content
Glama

Edit a list

update_list
DestructiveIdempotent

Change a list: rename it (new_name), set or clear its description, set who can see it (visibility: private, link = anyone with the share link, public = also on the user's public page), and edit one entry's note or position. Only change visibility when the user asks; public list names and descriptions are checked before they go on the public page.

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": {
      "list_name": "<list_name>"
    },
    "name": "update_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemNoOne entry on the list to change. It must already be on the list (use add_to_list first).
new_nameNoNew name for the list
list_nameYesThe list to change (case-insensitive)
visibilityNoWho can see the list
descriptionNoNew description; an empty string clears it

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / item / properties / media_type / enum
      Previous value: -[
      -  "book",
      -  "movie",
      -  "album",
      -  "show",
      -  "anime",
      -  "podcast",
      -  "game",
      -  "manga",
      -  "comic"
      -]New value: +[
      +  "book",
      +  "movie",
      +  "album",
      +  "show",
      +  "anime",
      +  "podcast",
      +  "game",
      +  "manga",
      +  "comic",
      +  "boardgame"
      +]
  2. Changed1 schema field changed
    • changedInput schema / properties / item / properties / media_type / enum
      Previous value: -[
      -  "book",
      -  "movie",
      -  "album",
      -  "show",
      -  "anime",
      -  "podcast",
      -  "game",
      -  "manga"
      -]New value: +[
      +  "book",
      +  "movie",
      +  "album",
      +  "show",
      +  "anime",
      +  "podcast",
      +  "game",
      +  "manga",
      +  "comic"
      +]
  3. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true and readOnlyHint=false, so the mutation profile is known. The description adds value beyond that: it defines the three visibility levels in user-facing terms and warns that public list names/descriptions are moderated before appearing on the public page, which is meaningful consequence-of-action context not encoded anywhere else.

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 scope is front-loaded in the opening clause and every clause maps to a distinct parameter. The visibility parenthetical is long but each element carries information; the moderation sentence is a genuine caution rather than filler.

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?

For a 5-parameter tool with a nested item object and no output schema, the description covers the top-level operations, the visibility semantics, and the public-page consequence. It does not state whether multiple changes can be combined in one call or what the response returns, but these are minor gaps given the 100% schema coverage.

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 coverage is 100%, so the baseline is 3, but the description genuinely adds meaning: it spells out what 'link' and 'public' mean ('anyone with the share link' vs 'also on the user's public page'), which the bare enum values do not convey. It also clarifies that the item edit is limited to note or position of one existing entry.

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 opens with a specific verb+resource ('Change a list') and enumerates the exact editable facets: rename via new_name, set/clear description, set visibility, and edit one entry's note or position. It does not name the sibling tools it is not (create_list, delete_list, add_to_list, remove_from_list), so an agent must infer the boundaries from sibling names alone.

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?

'Only change visibility when the user asks' is a real usage constraint that prevents an agent from silently making a list public. However, there is no explicit routing to alternatives — nothing says to use add_to_list to add entries or create_list/delete_list for other lifecycle operations, even though the schema hints at add_to_list for entries not yet on the list.

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