Skip to main content
Glama

Find a track in your collections

search_collections
Read-onlyIdempotent

Find tracks inside your own collections by title, original title, creator, tag or the note on a collection item. Each result names the collections that hold the track. Returns at most 50 per page; cursor gives the next page. capped is true when the match list reached its limit, so a narrower query can find more.

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": {
      "query": "<query>"
    },
    "name": "search_collections"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWords to find. The last word also matches as a prefix.
cursorNoPass the cursor from the previous page.
include_archivedNoAlso search archived collections.

Output Schema

NameRequiredDescriptionDefault
moreYes
cappedYes
cursorYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior, yet the description still adds non-obvious operational context: a 50-result page cap, cursor-based continuation, and the meaning of the 'capped' flag including the counterintuitive consequence that broadening results requires narrowing the query. Return shape is left to the output schema, which is appropriate given one exists.

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?

Four compact sentences with no filler. Scope comes first, then result annotation, then pagination limits, then the truncation caveat — a logical, front-loaded order where each sentence carries distinct information.

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 an output schema present, explaining return values is unnecessary, and the description goes further than required by disclosing the page cap and the 'capped' semantics. The only shortfall is the absent contrast with sibling search tools, which matters given a crowded collection of search-related tools.

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 coverage is 100%, so all three parameters are already documented, including prefix-matching and cursor reuse. The description's enumeration of searchable fields does add real meaning about what 'query' actually scans, but that is the only increment beyond the schema.

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 ('find tracks inside your own collections') and enumerates the matched fields (title, original title, creator, tag, item note). The phrase 'your own collections' implicitly scopes it away from library-wide tools like search_tracks, but no sibling is named explicitly, so an agent must infer the boundary.

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 context is implied by the 'your own collections' framing, and the closing sentence gives actionable advice on refining a query when 'capped' is true. However, it never states when to prefer search_tracks, find_similar, or list_collections instead, leaving the alternative-selection decision to inference.

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