Skip to main content
Glama

update_list

Rename a Trello list, change its position to top, bottom, or a specific number, or archive/unarchive it.

Instructions

Rename a list, change its position (top, bottom, or a number), or archive/unarchive it.

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
posNotop, bottom, or a number
langNoISO 639-1 code of the language the user is writing in (e.g. en, ru, uk). Always pass it: server messages are returned in this language.
nameNo
closedNo
listIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already establish this mutates state (readOnlyHint=false) without being destructive (destructiveHint=false), and the description's mention of archive/unarchive is consistent with that. It adds no further behavioral context such as permission requirements, whether position changes reorder other lists, or whether archiving affects contained cards. Given the annotations cover the safety profile, this is adequate but thin.

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?

One sentence, front-loaded with the primary action, with parenthetical detail only where the value format is ambiguous. Nothing is padded.

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?

For a five-parameter mutation tool with no output schema, the description covers the actions but omits the language parameter's purpose (left to the schema) and gives no indication of return values or side effects on sibling list ordering. The unresolved overlap with archive_list is the main completeness gap.

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 coverage is only 40%, so the description must carry weight: it does map position to the pos parameter (top, bottom, or a number) and archive/unarchive to closed, and rename to name, which genuinely compensates for the undescribed name and closed fields. However listId is never explained, and the mapping of 'archive/unarchive' to the closed boolean is left implicit.

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?

States a specific verb set and resource: rename, reposition (top/bottom/number), and archive/unarchive a list. This is concrete enough to distinguish it from get_lists or create_list. It stops short of differentiating itself from the sibling archive_list, which appears to overlap with the archive/unarchive capability named here.

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?

The enumerated operations imply when the tool applies, but there is no explicit when-to-use or when-not-to-use guidance. Most notably it never clarifies the relationship with the sibling archive_list, leaving an agent to guess which tool to pick for archiving.

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