get_genre_tracksFetch tracks for a genre ID or slug, newest first, with page, count, and duration filters to browse audio by genre.
Tracks of one genre, newest first.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page, starting at 1 | |
| count | No | Items per page (max 50) | |
| genre | Yes | Genre id or slug from list_genres | |
| duration_max | No | ||
| duration_min | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds value by specifying the sorting order ('newest first'), which is a key behavioral trait not found in the annotations. Since the annotations only cover safety (readOnlyHint), this description provides essential functional context.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The definition is highly concise, stating the core function and the primary sorting mechanism in a single, efficient sentence with no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
While it defines the core output, it is not fully complete. It doesn't guide the agent on how to optimally use the five input parameters (e.g., setting duration filters or pagination) to achieve specific results beyond the basic retrieval.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description is extremely brief and only applies to the general concept of 'genre.' Given that 40% of the input schema descriptions are missing, the description offers no semantic guidance to help an agent utilize parameters like `duration_min` or `count` effectively.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the resource being returned ('Tracks') and the specific condition applied ('of one genre'). It differentiates this tool by specifying the sorting behavior ('newest first') which aids in selection.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The usage is implied by the function name and the list of sibling tools. It lacks explicit guidance on when this specific tool should be called versus a generic search or list operation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.