Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

soundcloud_search

Search SoundCloud tracks by text query to retrieve matching titles, artwork, engagement counts, and uploader data from SoundCloud's public JSON API.

Instructions

Search SoundCloud tracks. Returns tracks matching a query: title, artwork, playback/likes/comment/repost counts, and uploader. Public data sourced from SoundCloud's own JSON API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of tracks to return (default 20, max 50)
queryYesSearch text

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.14.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does reveal that the data is public and sourced from SoundCloud's own API, which implies a read-only, authentication-free operation, and it usefully lists playback/likes/comment/repost counts. However, it doesn't disclose absence of audio streams, pagination, rate limit, or any side-effect expectations.

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 two sentences and wastes no words. The primary scoping ('Search SoundCloud tracks. Returns tracks matching a query') comes first, and the rest is a compact, useful list of returned data.

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 query+limit search tool, the description provides adequate context for an agent to call the tool successfully. Though there is no output schema, it lists the major fields returned. It doesn't need to detail every field or describe internal API mechanics in this situation.

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?

The schema covers 100% of the parameters, so the baseline is 3. The description adds no extra meaning beyond the schema for 'limit' or 'query'; it describes return fields rather than parameter semantics.

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 clearly identifies the specific action and resource: 'Search SoundCloud tracks' and enumerates what is returned. It is distinct enough in that it is a keyword-search tool, but it doesn't explicitly draw the boundary against sibling tools like soundcloud_track and soundcloud_user_tracks.

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?

There is no guidance on when to use this tool versus alternative SoundCloud tools. The description doesn't state that detail retrieval should use soundcloud_track or that user-scoped retrieval should use soundcloud_user_tracks, so the agent must infer the correct usage.

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