AINSOF

browse_playlist

Use when the user explicitly asks for an AINSOF editorial playlist by its exact name or key, such as Noir After Midnight or Sports. Return the website's matching tracks in order. For a genre or mood tag use browse_tag; for a creative brief use search_music. Continue with the same name or key, page size and cursor.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "playlist_key": "<playlist_key>"
    },
    "name": "browse_playlist"
  }
}

Input Schema

Name	Required	Description
`cursor`	No
`page_size`	No	Number of primary tracks per page; separately displayed versions may add rows.
`playlist_key`	Yes	Exact editorial playlist name or key.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4.4/5.0

Behavior3/5

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

The description adds real behavior beyond annotations: results are returned in the website's order and pagination is cursor-based and continuable. However, annotations declare readOnlyHint=false while the description frames this purely as a retrieval ('Return the website's matching tracks'), and no side effect, logging, or auth requirement is disclosed to resolve that tension. The description does not contradict the annotations outright, but the unexplained non-read-only hint is left unaddressed.

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 sentences, front-loaded with the trigger condition, followed by output semantics and sibling routing. No sentence is redundant and the alternative-tool guidance is tightly packed.

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 still conveys ordering, pagination, and the exact-match requirement, which is most of what an agent needs. It omits failure behavior for an unrecognized playlist name/key and says nothing about the non-read-only annotation, which would matter when deciding to invoke it.

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 67% and the only undocumented parameter is cursor, which the description explains pragmatically by saying to continue with the same cursor. It also adds examples of valid playlist_key values that the schema's one-line description lacks.

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?

Names a specific verb (browse/return) and a specific resource (AINSOF editorial playlist) scoped to an exact name or key, with concrete examples ('Noir After Midnight or Sports'). It also explicitly separates itself from browse_tag and search_music, so an agent can distinguish it from siblings without consulting 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?

States the trigger condition ('user explicitly asks ... by its exact name or key') and routes the two adjacent cases to named alternatives: genre/mood tag to browse_tag, creative brief to search_music. It also tells the agent how to continue paging ('same name or key, page size and cursor').

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

All AINSOF 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?