Skip to main content
Glama

update_list

Edit a custom game list by changing its title, description, ranked or publish status, and adding or removing games by slug or ID. Only supplied fields are updated.

Instructions

Edit your own custom list: title, description, add_games / remove_games (slugs or ids), ranked and publish ("true"/"false"). Only the fields you pass change.

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_id": "<list_id>"
    },
    "name": "update_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNo
rankedNo
list_idYes
publishNo
add_gamesNo
descriptionNo
remove_gamesNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description does useful work by declaring this is a partial mutation (only supplied fields change) and by constraining scope to 'your own' list. It says nothing about required permissions, whether publish or ranked changes are reversible, how add_games and remove_games interact in one call, or what the response contains.

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?

Two short sentences, front-loaded with the verb and resource, then the field list, then the partial-update rule. Nothing is wasted and the most important behavior is stated last for emphasis.

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 7-parameter mutation with an output schema and no annotations, the description covers the field set, accepted input formats, ownership scope, and partial-update behavior. The remaining gaps (ranked values, permission requirements, add/remove conflict behavior) are modest rather than disqualifying.

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 0%, so the description must compensate, and it largely does: it names title, description, add_games, remove_games, ranked, and publish, and clarifies that game references accept slugs or ids and that publish takes "true"/"false". The one gap is ranked, whose accepted values or meaning are not explained despite being a string parameter.

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 states a specific verb (Edit) and resource (your own custom list) and enumerates the editable fields, which clearly separates it from create_list, delete_list, and get_list. It stops short of naming those siblings explicitly, but the operation is unambiguous.

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?

Usage is implied: edit an existing list you own, and 'Only the fields you pass change' signals partial-update semantics. There is no explicit when-not guidance or mention of alternatives like create_list for new lists, leaving the agent to infer context.

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