Skip to main content
Glama

Update a collection item

update_collection_item
Destructive

Change one item in a collection: set or clear its note (up to 500 characters; an empty note clears it), record the changes made to the track in modifications, or move it to a position in the track order. Fields left out are unchanged.

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": {
      "collection_id": "<collection_id>",
      "track_id": "<track_id>"
    },
    "name": "update_collection_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNo
positionNo
revisionNo
track_idYes
collection_idYes
modificationsNo

Output Schema

NameRequiredDescriptionDefault
idYes
kindYes
nameYes
itemsYes
createdYes
updatedYes
revisionYes
read_onlyYestrue when a lapsed Pro plan has made this collection view-and-export only.
commercialYes
archived_atYesWhen the collection was archived, or null.
descriptionYesOne line of plain text, or null.
credits_headingYesThe credits block heading, or null for the default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is partly covered. The description adds genuinely new behavioral context beyond them: merge semantics ('Fields left out are unchanged') and the clearing behavior of an empty note. It still does not explain why the operation is flagged destructive or what happens on failure, but the added context is substantive.

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?

A single front-loaded sentence that leads with the action and then enumerates the mutable aspects with parenthetical detail. Dense but readable, with no filler; it could be split for scannability but every clause carries information.

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?

An output schema exists, so return values need not be described. However, for a 6-parameter mutation tool with destructiveHint=true, the description omits any treatment of revision semantics, error/failure behavior, and the consequence of destructive changes, leaving meaningful gaps.

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 0%, so the description must carry all parameter meaning. It explains note (500-char cap, empty clears), modifications (records track changes), and position (target index in track order), but leaves revision, track_id, and collection_id completely unexplained — revision in particular is non-obvious and potentially concurrency-related.

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 and resource ('Change one item in a collection') and enumerates the three concrete mutations available: setting/clearing a note, recording modifications, and moving to a position. It is clear what the tool does, but it never contrasts itself with siblings like update_collection or reorder_collection, leaving that distinction to be inferred from the item-level framing.

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 only implied: the enumeration of updatable aspects suggests when to reach for this tool, and 'Fields left out are unchanged' implicitly promises partial-update safety. There is no explicit when-to-use or when-not-to-use guidance relative to update_collection (collection-level changes) or reorder_collection, and no stated prerequisites.

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