Skip to main content
Glama

Remove a track from a collection

remove_from_collection
Destructive

Remove a track from one of your editable collections. This changes the collection but does not delete the track from the catalog.

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": "remove_from_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
track_idYes
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

A3.6/5.0
Behavior4/5

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

Annotations already declare destructive=true, readOnly=false, idempotent=false, so the safety profile is known. The description adds real value beyond that by clarifying blast radius: only the collection is modified and the track itself survives in the catalog. It does not cover error behavior for tracks not in the collection, which keeps it from a 5.

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 the second sentence is a non-destructive-scope clarification that earns its place. No filler or repetition.

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?

An output schema exists, so return values need not be described, and the operation itself is simple (two required IDs). The description covers purpose, mutability scope, and precondition adequately; only parameter-level detail and failure modes are missing, which is minor for a tool this simple.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the burden of explaining the two required parameters, and it explains neither. It never says what collection_id or track_id accept (ID format, ownership, minLength constraint), leaving only the parameter names to infer meaning.

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 and resource ('Remove a track from ... collections') and scopes it to editable collections, which cleanly separates it from the add_to_collection/add_many_to_collection siblings. It does not explicitly name an alternative tool, so it stops short of a 5.

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 phrase 'one of your editable collections' implies a precondition (the collection must be writable by the caller), which is useful when-to-use context. There is no explicit guidance on when to prefer this over update_collection_item or delete_collection, so usage is only implied.

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