Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

soundcloud_track

Retrieve detailed information about a SoundCloud track by its URL to validate or enrich track data.

Instructions

soundcloud: Track. GET /v1/soundcloud/track. Gets detailed information about a SoundCloud track/song by URL. Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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": {
      "url": "<url>"
    },
    "name": "soundcloud_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesSoundCloud track URL.

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 behavioral burden; it does add genuine context by spelling out the credit cost on success and that errors, blocked/timed-out requests, invalid requests and cache hits are free. However, it discloses nothing about authentication, rate limits, retry behavior, or what happens on a not-found result beyond an oblique pointer to 'that operation's published cost.'

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 purpose sentence is front-loaded and efficient, but the opening 'soundcloud: Track. GET /v1/soundcloud/track.' duplicates the tool name and is pure overhead. The three-sentence cost paragraph is relevant yet disproportionately long for a one-parameter read tool.

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?

There is no output schema, so the description is the only place an agent could learn what 'detailed information' actually contains, and it does not say. The cost and cache semantics are covered well, but return shape and failure modes are left unspecified for a tool an agent must call blind.

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% and the single url parameter already documents itself with an example, so the 3 baseline applies. The description adds nothing beyond 'by URL' — no URL format rules, no accepted variants such as private or short links.

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 specific verb and resource — 'Gets detailed information about a SoundCloud track/song by URL' — which is unambiguous and separable from siblings like soundcloud_artist or soundcloud_artist_tracks. The leading 'soundcloud: Track. GET /v1/soundcloud/track.' merely restates the name and route but does not undermine the clarity.

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: an agent can infer it should call this when it has a SoundCloud track URL, but the description never says when to pick this over soundcloud_artist_tracks or a search tool, nor does it state any prerequisites or exclusions. The cost model hints at a paid lookup but does not translate into routing guidance.

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