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

mixcloud-mcp-server

by muntag
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

favorite_show

Add a Mixcloud show to favorites using its key, or set undo=true to remove it from favorites. Manage saved shows through an MCP client.

Instructions

Favorite a show ('/spartacus/party-time/'); undo=True removes it from favorites.

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": "favorite_show"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes
undoNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, yet it does disclose a genuinely useful behavioral trait: the operation is reversible via undo=True. It omits auth requirements, rate limits, and whether the key must reference an existing show, so it is only partially transparent for a mutation tool.

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 compact sentence with the primary action front-loaded and the undo semantics appended; nothing is wasted. It is arguably a touch terse for a mutation tool, but the structure is efficient.

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

Completeness3/5

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

For a simple two-parameter mutation with no output schema, the core action and its reversal are covered adequately. However, missing auth/permission context and no confirmation of what the operation returns leaves it only minimally complete.

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 description coverage is 0%, so the description must compensate, and it largely does: the key format is illustrated with a concrete path example and the boolean undo parameter's effect is explained. Both parameters gain meaning beyond their bare names in the 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?

States a clear verb+resource ('Favorite a show') and includes a concrete key example, so the agent knows exactly what object it operates on. It does not explicitly distinguish itself from siblings like repost_show or listen_later, which are plausible confusions, so it stops short of a 5.

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 undo=True clause hints at how to reverse the action, but there is no guidance on when to favorite versus the neighboring follow_user/repost_show/listen_later tools, nor any prerequisites. Usage must be inferred.

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