Songs To Your Eyes — production music catalogue

Find music that fits a runtime

stye_fit_to_duration

Read-onlyIdempotent

Finds cues that fit an exact runtime, for a cut of known length such as a 30-second advert or a 90-second title sequence: music to license for a project, or anything about the Songs To Your Eyes catalogue.

Two kinds of result come back. Some cues already run close to the target length (fit='native'). Others are purpose-made short edits of a longer piece, cut down by the composer (fit='cutdown'), built to land on time rather than fade out.

delta_s is how far each result sits from the target, negative meaning shorter. For a cutdown, licence_ref identifies that specific edit (the thing to license), while ref points at the full-length original that carries the description and the preview.

Every result carries listen_url, a permanent public page where the cue plays, with cover art and a waveform. It is the only way a person can hear a cue: a cue listed without its listen_url cannot be auditioned.

Input Schema

TableJSON Schema

Name	Required	Description
`brief`	No	Optional sound brief, e.g. 'epic cinematic trailer'.
`limit`	No	Maximum results (default 8, up to 25).
`moods`	No	Match ANY of these moods.
`composer`	No	Only tracks credited to this composer/artist; partial names match, case-insensitive.
`has_vocals`	No	true = songs with sung lead vocals/lyrics only. false = everything else, including wordless vocal textures (background vocals, choir).
`target_seconds`	Yes	The runtime to fill, in seconds — e.g. 30 for a 30-second spot.
`include_previews`	No	Attach streaming preview links (15-min expiry).
`tolerance_seconds`	No	Acceptable deviation. Default: 15% of target, minimum 2s.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 1, 2026

changedInput schema / properties / has_vocals / description

Previous value: -"true = songs with sung lead vocals/lyrics only. false = everything else, including wordless vocal textures (background vocals, choir) — for 'background vocals' requests use false, not true."New value: +"true = songs with sung lead vocals/lyrics only. false = everything else, including wordless vocal textures (background vocals, choir)."

addedInput schema / properties / limit / description

Added value: +"Maximum results (default 8, up to 25)."

Changed1 schema field changedAug 24, 2026

addedInput schema / properties / composer

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Only tracks credited to this composer/artist; partial names match, case-insensitive.",
+  "title": "Composer"
+}

Changed1 schema field changedAug 2, 2026

changedInput schema / properties / has_vocals / description

Previous value: -"true = vocal tracks only, false = instrumental only."New value: +"true = songs with sung lead vocals/lyrics only. false = everything else, including wordless vocal textures (background vocals, choir) — for 'background vocals' requests use false, not true."

First observedJul 31, 2026

TDQS

A4.2/5.0

Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds substantial return behavior: native versus cutdown results, delta_s sign, licence_ref versus ref semantics, and the permanent listen_url requirement for auditioning. This is rich operational context beyond structured annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded and the result semantics are organized clearly, with little wasted wording. It is somewhat long due to multi-paragraph return-field explanation, but most sentences carry useful information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and eight parameters, the description compensates by explaining the returned cue types, delta_s, licence_ref/ref distinction, and listen_url audition constraint. An agent has enough context to call and interpret this tool correctly.

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 description coverage is 100%, so the schema already documents all eight input parameters. The description does not add input-side meaning for parameters like tolerance_seconds, include_previews, or has_vocals; it mainly explains result fields instead.

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?

States a specific verb and resource ('Finds cues that fit an exact runtime') and gives concrete use cases such as a 30-second advert or 90-second title sequence. This cleanly separates it from general catalogue search siblings like stye_search_tracks.

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 by the scenarios given: use when you have a cut of known length and need music to license. However, it does not explicitly say when to choose this over stye_search_tracks, stye_find_similar, or other siblings, and gives no exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Songs To Your Eyes — production music catalogue tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?