Skip to main content
Glama

Find ready-made tracks

find_tracks
Read-onlyIdempotent

Find ready-made Tuney tracks that match a brief. Results are instant and previews are free.

    Give either a free-text prompt (for example "warm acoustic guitar for a travel vlog intro") or
    exact genre, mood and tempo values from list_styles. Each result has a cue_id and a preview
    URL. Pass the returned search_id to get more results for the same brief. Use adjust_track
    to change length or key, and download_track for the final file (that costs credits).
    

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_tracks"
  }
}

Input Schema

NameRequiredDescriptionDefault
moodNo
genreNo
limitNo
tempoNo
promptNo
search_idNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the description wisely adds economics instead: previews are free while downloads cost credits, and search_id enables paginated continuation. It does not say how long a search_id stays valid or how 'instant' results are bounded, which is the only remaining gap for an openWorld tool.

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?

The core capability is front-loaded in the first sentence, followed by input modes, then return fields, then pagination, then next-step routing. Every sentence carries a distinct fact with no 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?

An output schema exists, so return values needn't be explained, yet the description still usefully flags cue_id, preview URL, and search_id as the key handles. The main remaining gap is the undocumented limit parameter and no statement about whether prompt can be combined with structured filters or is strictly exclusive.

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?

With 0% schema description coverage, the description has to carry all parameter meaning, and it does for prompt (with a worked example), genre/mood/tempo (values come from list_styles), and search_id (returned from a prior call to fetch more). It says nothing about the 'limit' parameter, leaving one of six parameters undocumented everywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Find ready-made Tuney tracks') plus the selection criterion ('that match a brief'). The word 'ready-made' implicitly separates it from the generative sibling, so an agent can distinguish this from generate_track without inspecting schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly names the two input modes (free-text prompt vs. exact genre/mood/tempo values from list_styles), routes refinement to adjust_track, and routes final acquisition to download_track. Alternatives are named with the condition that selects them, leaving little 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.