Skip to main content
Glama
Sign In
mixcloud-mcp-server

mixcloud-mcp-server

by muntag
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

browse

Retrieve site-wide lists of popular, hot, or new Mixcloud shows, with limit and offset controls for paging.

Instructions

Site-wide lists: popular, hot or new shows.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "browse"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
list_nameNopopular

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden and delivers almost nothing. It does not disclose whether results are paginated (despite limit/offset), how lists are ordered, or whether authentication is required for this read.

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?

A single short sentence with no filler, and the key scoping qualifier ('site-wide') is front-loaded. It is efficient, though arguably under-specified rather than optimally concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be explained, but the definition still leaves major gaps: three undocumented parameters, no annotation coverage, and no pagination or auth context. For a 3-param tool it is too thin to guide correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate and largely fails. It echoes the list_name enum values (popular, hot, new) but says nothing about limit or offset pagination semantics, leaving two of three parameters unexplained anywhere.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource ('site-wide lists') and the variant values ('popular, hot or new shows'), which lets an agent separate it from user_shows and genre_shows. However, it never states the action verb and 'browse' alone is vague, so the purpose is only implied rather than explicit.

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 statement of when to use this tool versus siblings like search, user_shows, or genre_shows. The word 'site-wide' hints at a distinction but the agent must infer it; no exclusions or prerequisites are given.

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