Skip to main content
Glama

Add several tracks to a collection

add_many_to_collection

Add 1 to 25 tracks atomically. Existing tracks are reported as already present; no new track is added if the 500-item cap or the CC BY-NC commercial rule would fail.

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

Input Schema

NameRequiredDescriptionDefault
tracksYes
revisionNo
collection_idYes

Output Schema

NameRequiredDescriptionDefault
idYes
kindYes
nameYes
itemsYes
createdYes
resultsYes
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 only declare the safety profile (readOnly=false, destructive=false, idempotent=false), so the description adds real value: all-or-nothing atomicity, duplicate tracks being reported as 'already present' rather than re-added, a 500-item collection cap, and a CC BY-NC commercial licensing rule that can block the write. Remaining gaps are the concurrency role of revision and any permission/auth requirements.

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 dense sentences with no filler; the batch size and atomicity constraint come first, followed by the failure conditions. Nothing is repeated from the schema or annotations verbatim.

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 explained, and the description covers the main behavioral risks of a batch mutation: atomicity, duplicates, capacity, and licensing. It falls short only on revision semantics and permission prerequisites, which an agent needs before calling a non-idempotent write.

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 must carry parameter meaning, and it only partly does: it explains the tracks array size and duplicate handling, but the required collection_id and the optional revision parameter get no explanation at all. revision is clearly an optimistic-concurrency token, and leaving it undefined on a non-idempotent mutation is a significant omission.

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 ('Add ... tracks to a collection') and pins the scope with '1 to 25 tracks atomically', which implicitly separates it from the single-item add_to_collection sibling. It stops short of naming that sibling explicitly, so the differentiation requires a small inference.

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 '1 to 25' range and 'atomically' wording imply this is the bulk path versus a single-track tool, so usage is suggested rather than stated. There is no explicit when-to-use/when-not statement, no mention of preferring the single-add tool for one track, and no prerequisites such as required permissions.

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