Skip to main content
Glama
Sign In
SoundCloud MCP Server

SoundCloud MCP Server

by jamiew
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Next page

next_page
Read-only

Fetches the next page of SoundCloud API results by following a next_href link from a previous response. Use it to continue paginated search or discovery results.

Instructions

Fetch next_href with a GET to the SoundCloud API (https://developers.soundcloud.com/docs/api/guide).

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": {
      "nextHref": "<nextHref>"
    },
    "name": "next_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
verboseNoReturn every field SoundCloud sends, such as descriptions, not the compact summary
nextHrefYesThe next_href from a previous result

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.2

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that the underlying call is a GET and points to the API guide, but it does not say what comes back (results plus possibly a further next_href) or anything about rate limits or auth, which matters for an open-world 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 front-loaded sentence that states the mechanism and where to find documentation. The embedded developer-docs URL is mildly incidental but cheap and potentially useful; nothing is padded.

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

Completeness4/5

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

For a two-parameter read-only pagination tool with full schema coverage and clear annotations, little is missing. The only real gap is the absence of an output schema combined with no statement of what the response contains, which an agent would want in order to know whether more pages follow.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters—nextHref (a URI taken from a previous result) and verbose (full vs. compact fields)—are already documented. The description adds no semantics beyond that, so baseline 3 applies.

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 names a concrete verb and object—fetch the next_href via GET against the SoundCloud API—so an agent knows this is a pagination read. It does not name or contrast any sibling, though none of the listed siblings (search_*, get_*) perform pagination, so confusion risk is low.

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 only implied: the phrase 'Fetch next_href' together with the schema note that it comes 'from a previous result' suggests it should be called when a prior response carries a next_href. There is no explicit when-to-use statement, no mention of what to do when next_href is absent, and no stated alternative.

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