Skip to main content
Glama

Add a track to a collection

add_to_collection

Add a track returned by search to one of your editable collections. A collection has at most 500 tracks. A CC BY-NC track cannot be added to a commercial collection; use another track or mark the collection not commercial.

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

Input Schema

NameRequiredDescriptionDefault
noteNo
revisionNoCurrent collection revision when coordinating concurrent edits.
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 non-destructive, non-idempotent, closed-world writes, so safety is largely covered. The description nonetheless adds genuinely useful behavior beyond them: a hard 500-track ceiling per collection, the requirement that the collection be editable, and the CC BY-NC licensing restriction with a remediation path. It omits duplicate-handling behavior, which matters given idempotentHint=false.

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, each carrying a distinct constraint: the core action, the capacity limit, and the licensing rule. The primary action is front-loaded and there is no redundant restatement of the title or schema.

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 four parameters, one undocumented revision field, and an output schema present, the description covers the important domain constraints an agent needs before calling: editability, the 500-track cap, and licensing. The remaining gap is duplicate handling and how 'revision' should be used for concurrency, which the description leaves entirely to the schema.

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 only 25% — only 'revision' carries any schema documentation, and the description does not compensate. Neither 'note' (a 500-char annotation field) nor the semantics of 'collection_id'/'track_id' are explained in the description, so the agent learns nothing about the two optional parameters or the revision-based concurrency model.

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?

"Add a track returned by search to one of your editable collections" gives a specific verb (add), resource (track), and target (editable collection), and the singular 'a track' implicitly separates it from add_many_to_collection. It stops short of naming a sibling outright or stating what happens with duplicate tracks, so it is clear but not maximally differentiating.

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 through 'a track returned by search' and 'one of your editable collections', which tells the agent the source of the track and the permission requirement. However, there is no explicit statement of when to prefer this over add_many_to_collection or remove_from_collection, and no exclusion guidance beyond the licensing rule.

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