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

mixcloud-mcp-server

by muntag
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

user_shows

Retrieve paginated Mixcloud user shows by key, with optional limit, since, until, and offset filters.

Instructions

List a user's shows. key: '/spartacus/'.

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": {
      "key": "<key>"
    },
    "name": "user_shows"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
limitNo
sinceNo
untilNo
offsetNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/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 burden of behavioral disclosure. It does not state that this is a read-only operation, whether authentication is required, how pagination works, or any rate limits. The output schema covers return values, but input-side behavior remains opaque.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short and front-loads the main action. However, the second sentence 'key: '/spartacus/'.' is cryptic and does not clearly earn its place, making the overall structure minimally adequate rather than polished.

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?

For a five-parameter tool with no annotations and 0% schema description coverage, the description is far too sparse. While an output schema exists and need not be explained, the input semantics—especially for limit, since, until, and offset—are missing entirely.

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 should compensate for five undocumented parameters. It only gives a cryptic example for 'key' ('/spartacus/') and says nothing about limit, since, until, or offset, leaving their semantics entirely to the bare schema.

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 states a clear verb and resource: 'List a user's shows.' This distinguishes it from most siblings, though it does not explicitly differentiate from search or get_user. The cryptic key example '/spartacus/' adds little to the core purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the name and description: use this to retrieve a user's shows. However, there is no explicit when-to-use guidance, no mention of when not to use it, and no named alternative such as search or get_user.

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