Skip to main content
Glama

Add to a list

add_to_list
Idempotent

Add a library item to a list by title. Creates the list if it does not exist. The item must already be in the library (use add_item first if not).

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>",
      "media_type": "<media_type>"
    },
    "name": "add_to_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoOptional note about why this item is on the list
titleNoThe library item title (exact title preferred; an ambiguous partial match returns candidates with ids instead of guessing)
item_idNoLibrary item id (UUID), as shown by get_details. When given, title is ignored and the row is addressed exactly.
list_nameYesThe list to add to (case-insensitive; created if missing)
media_typeYesType of media

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / 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 / 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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the safety profile is covered. The description adds meaningful behavior beyond them: implicit list creation and the requirement that the parent item already exist. It says nothing about failure modes or permission needs, but the added side-effect disclosure is the substantive part.

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?

Three short sentences, front-loaded with the action and ordered by what an agent needs first: what it does, what it creates, what must already exist. No filler or redundancy.

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 write tool with no output schema, the description covers action, side effects, and preconditions, which is enough to call it correctly. The remaining gap is disambiguation from the similarly named shelf/pin siblings, which matters given how many near-duplicate add tools exist.

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 description coverage is 100%, so each parameter (including the ambiguity-handling behavior of title and the UUID precedence of item_id) is already fully documented. The description's framing "by title" is slightly narrower than the schema, which allows exact addressing via item_id, so it adds no meaning and mildly undersells an option.

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?

States a specific verb and resource (add a library item to a list) plus the key creation side effect, and names the sibling tool to use when the prerequisite is unmet (add_item). An agent can distinguish it from add_item without opening either 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?

Gives an explicit prerequisite and fallback ("The item must already be in the library (use add_item first if not)") and clarifies that the list is auto-created, which is real when-to-use guidance. It does not address the more confusing overlap with add_to_shelf or pin_to_page, so the list-versus-shelf distinction is left unresolved.

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