Skip to main content
Glama

Reorder a collection

reorder_collection
Destructive

Set the complete track order. tracks must contain every existing item exactly once; supply revision to avoid overwriting another edit.

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>",
      "tracks": "<tracks>"
    },
    "name": "reorder_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
tracksYes
revisionNo
collection_idYes

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

A4.3/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and idempotentHint=false; the description adds the critical mechanics behind that: this is a whole-order replacement where the supplied list must cover every existing item exactly once, and revision provides optimistic concurrency protection. That is exactly the operational context an agent needs before a destructive write, beyond what the structured fields convey.

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 sentences, front-loaded with the action and immediately followed by the constraint and the concurrency hint. No filler or redundant restatement of the title.

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?

With annotations covering the safety profile and an output schema covering return values, the description supplies the missing replacement semantics and concurrency guidance. It could go slightly further on failure behavior (e.g., what happens if the list is incomplete or revision is stale), but it is complete enough to call correctly.

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 carry parameter meaning; it explains tracks (complete set, each item exactly once) and revision (concurrency guard to avoid overwriting another edit). collection_id is left implicit, which is a minor gap given its obvious role, but the two semantically ambiguous parameters are covered well.

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?

"Set the complete track order" names a specific verb (set/reorder) and resource (collection track order), making clear this is a full-order replacement rather than an incremental add/remove. It does not explicitly distinguish itself from siblings like update_collection or update_collection_item, but the "complete track order" phrasing implies the distinction.

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?

The description gives a concrete precondition for use (tracks must contain every existing item exactly once) and an explicit recommendation to supply revision to avoid clobbering concurrent edits. It stops short of naming alternatives (add_to_collection, remove_from_collection) or stating when-not to use it.

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