Skip to main content
Glama
SoundCloud MCP Server

SoundCloud MCP Server

by jamiew

Like track

like_track
Idempotent

Like a SoundCloud track by track ID to add it to your account’s liked tracks.

Instructions

Like a track.

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

Input Schema

NameRequiredDescriptionDefault
trackIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.1.2
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / properties / trackId / minimum
      Removed value: -1
    • changedInput schema / properties / trackId / type
      Previous value: -"number"New value: +[
      +  "string",
      +  "number"
      +]
  2. First observedv1.0.0

TDQS

D1.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing on top: it does not say whether liking is idempotent (safe to repeat), whether it requires an authenticated user, or what state change results. With annotations carrying most of the burden, the description still contributes zero incremental context.

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

Conciseness2/5

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

At three words the description is not verbose but is severely under-specified rather than concise; brevity here removes information rather than eliminating waste. There is no structure or front-loaded detail because there is no detail at all.

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

Completeness1/5

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

For a mutation tool with no output schema and an undocumented required identifier, the description should explain the effect, authentication expectations, and identifier format. None of these are present, making it inadequate for 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% for the single required trackId parameter, and the schema allows either string or number without explanation. The description does not clarify whether trackId is a numeric ID, a URN, or a permalink URL, leaving a genuine ambiguity for the caller to resolve.

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

Purpose2/5

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

The description is 'Like a track.' which simply restates the tool name and title without adding any distinguishing detail. It does convey a verb+resource at a bare minimum, but an agent gains nothing it could not already infer from 'like_track', and no differentiation from unlike_track, repost_track, or like_playlist is offered.

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 tool, no prerequisites (e.g. authentication via connect_soundcloud), and no mention of the counterpart unlike_track for reversing the action. The agent must infer the entire usage context from the name alone.

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