Skip to main content
Glama
SoundCloud MCP Server

SoundCloud MCP Server

by jamiew

Sign out

sign_out
DestructiveIdempotent

Revoke the app’s SoundCloud access and delete its stored token to disconnect the account. Public search still works afterward.

Instructions

Revoke this app's SoundCloud access and delete the stored token. Public search still works afterward.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sign_out"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, so the description's job is to say what is destroyed and what survives. It does both: app access is revoked, the stored token is deleted, and unauthenticated public search remains functional. It does not spell out that all authenticated endpoints (get_my_likes, like_track, get_feed, etc.) will fail until re-connection, which is the practical risk an agent needs.

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

Conciseness5/5

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

Two short sentences, action first and post-condition second, with no redundant restatement of the title. Every clause carries information an agent would otherwise have to guess.

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 zero-parameter, no-output auth tool this covers the essentials: what is revoked, what is deleted, and what still works. The one gap is the recovery path — that the agent must call connect_soundcloud afterward to restore authenticated access.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. No misleading parameter claims are made.

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

Purpose5/5

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

States a specific verb+object pair: revoke this app's SoundCloud access and delete the stored token. It is unmistakably the inverse of the sibling connect_soundcloud and cannot be confused with any read tool such as auth_status or search_tracks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The consequence clause ('Public search still works afterward') effectively tells the agent what state exists after the call, which is the main usage decision here. It stops short of naming the follow-up path (connect_soundcloud to re-authenticate) or stating when an agent should avoid signing out.

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