Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_shows_search

Search Spotify podcast shows by term, with offset and limit pagination, to retrieve titles, publishers, descriptions, images, and Spotify URLs as clean JSON.

Instructions

Search Spotify shows. Searches Spotify podcast shows for the search term q, paged with offset (default 0) and limit (1 to 50). Each show has its title, URI, publisher, description, images and Spotify URL. Show matches appear under both results and shows. A missing q returns 400.

Input Schema

NameRequiredDescriptionDefault
qYesSearch term
limitNoResult limit, clamped to 1-50
offsetNoSearch offset

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

No annotations are provided, so the description carries the behavioral burden and does well: it discloses pagination defaults, the limit range, required q behavior with a 400 error, returned show fields, and that matches appear under both results and shows. It does not discuss authentication or rate limits.

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 description is four tight sentences, front-loaded with the core action and followed by paging, result shape, and error behavior. Every sentence adds useful operational information without fluff.

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?

For a simple three-parameter search tool with no output schema and no annotations, the description is largely complete: it explains paging, required input, error behavior, and the shape of returned shows. Minor gaps around authentication/rate limits remain.

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. The description still adds useful meaning by noting offset defaults to 0, limit is 1 to 50, and a missing q returns 400, though it does not elaborate much beyond the schema for q.

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?

The description states a specific verb and resource: searching Spotify podcast shows by term. It is clear what the tool does, though it does not explicitly distinguish itself from similarly named Spotify search siblings such as spotify_podcasts_search.

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

Usage Guidelines2/5

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

The description provides no explicit guidance on when to use this tool versus alternatives, nor does it name any sibling tools or exclusion conditions. Usage is only implied by the search-term parameter.

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

Deploy Server

Other Tools