Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

soundcloud_search

Search SoundCloud tracks by query and return structured results with title, artwork, genre, tags, duration, engagement counts, and uploader details for research or discovery.

Instructions

Search SoundCloud tracks. Searches SoundCloud tracks for query, in SoundCloud's default relevance order. limit defaults to 20 and is capped at 50. Each track has its title, artwork, genre, tags, duration_ms, play, like, comment and repost counts, and uploader details including follower count and verified status.

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

A3.5/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 full burden, and it does so well: it discloses ordering (SoundCloud's default relevance), the limit default and cap, and a detailed inventory of returned track fields including engagement counts and uploader verification. Auth requirements, rate limits, and pagination beyond the limit cap are not addressed, keeping it short of a 5.

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?

Front-loaded with the purpose, then dense useful detail about return payload. Minor redundancy: the second sentence re-states 'Searches SoundCloud tracks' and repeats the limit default/max already present in the 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?

With no output schema, the description usefully enumerates the return fields and ordering, so an agent knows what it will get back. Only auth/permission and pagination behavior are left unstated, which is a small gap for a read-only search.

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 coverage is 100%, so the schema already documents both `query` and `limit` including the default/cap. The description largely restates that limit information and adds little parameter-level meaning beyond noting relevance ordering. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb+resource ('Search SoundCloud tracks') and elaborates on the scope, so the agent immediately knows what it retrieves. It does not, however, contrast itself with siblings like soundcloud_track or soundcloud_user_tracks, which retrieve by ID or by user rather than by query.

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 implies usage ('searches ... for `query`') but gives no explicit when-to-use guidance, no prerequisites, and no mention of alternatives. An agent must infer that this is the entry point when it has free-text but no track/user ID.

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