Crawlora MCP

spotify_track

Read-only

Fetch Spotify track metadata by track uri, open.spotify.com track URL, or id. uri takes precedence; omitting both locators uses a built-in example track, so supply one for a specific song. Use spotify_tracks_search to find tracks or spotify_track_recommended for recommendations based on the track.

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

Input Schema

Name	Required	Description	Default
`id`	No	Spotify track ID, used when uri is omitted.
`uri`	No	Spotify track URI or open.spotify.com/track/... URL.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds two non-obvious behaviors the annotations cannot convey: uri takes precedence over id, and omitting both locators silently returns a built-in example track rather than erroring.

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 tight sentences, front-loaded with the verb and accepted inputs, then the precedence rule, then the sibling routing. 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.

Completeness5/5

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

With an output schema covering return values and annotations covering the safety profile, the description supplies exactly the missing pieces: accepted locator formats, precedence, the surprising default, and sibling alternatives. Nothing an agent needs to call it correctly is absent.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning beyond the schema: the precedence ordering between uri and id, and the default-example-track behavior when both are omitted, which the field descriptions do not state.

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 (Fetch) and resource (Spotify track metadata) and enumerates the three accepted locator forms. It also explicitly names the sibling it is not (spotify_tracks_search) and the recommendation variant, so an agent can distinguish it without opening 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?

Gives explicit routing: use spotify_tracks_search to find tracks, spotify_track_recommended for recommendations, and this tool to fetch by known locator. It also flags the condition that selects the fallback behavior (omitting both locators), leaving nothing to inference.

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

All Crawlora MCP 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?