Skip to main content
Glama
Sign In
SoundCloud MCP Server

SoundCloud MCP Server

by jamiew
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Repost track

repost_track
Idempotent

Repost a SoundCloud track to your followers so it appears in their feeds.

Instructions

Repost a track to the user's followers.

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": {
      "trackId": "<trackId>"
    },
    "name": "repost_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
trackIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.2

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=true, so the safety profile is covered. The description adds only the 'to the user's followers' consequence; it says nothing about authentication requirements, behavior when the track is already reposted, or error conditions for an invalid track.

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 front-loaded sentence with no filler or redundancy. It is efficient, though efficiency here comes partly from under-specification rather than disciplined brevity.

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 state-changing social action with one undocumented parameter and no output schema, the description should at minimum identify the ID format and any auth expectation. Given the rich sibling set of repost/unrepost variants, the definition is too thin to call it complete.

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% for a single required trackId that accepts string or number, and the description offers no clarification of whether this is a numeric ID, a URN, or a URL. With low schema coverage, the description needed to compensate and does not.

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 uses a specific verb plus resource ('Repost a track') and states the effect ('to the user's followers'), so the action is unambiguous. It does not distinguish this tool from close siblings such as repost_playlist or clarify its relationship to like_track/unrepost_track, which keeps it from 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?

There is no guidance on when to use this rather than like_track, repost_playlist, or the inverse unrepost_track, and no prerequisites or exclusions are given. The agent must infer the usage context entirely from the tool name and the sibling list.

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