@striderlabs/mcp-spotify

spotify_logout

Clear stored OAuth tokens to log out of Spotify, resetting authentication and enabling account switching.

Instructions

Log out of Spotify by clearing stored OAuth tokens. Use this to reset authentication or switch accounts.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 21, 2026

TDQS

A4.5/5.0

Behavior4/5

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

No annotations provided, so the description carries the full burden. It discloses that it clears stored OAuth tokens, which is a key behavioral side effect. It doesn't detail server-side invalidation or whether user data is affected, but the token clearing is adequately conveyed.

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 concise sentences that clearly state the action and its use cases. No redundancy or fluff; structure is optimal.

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?

The description covers purpose and usage, but lacks mention of side effects (e.g., whether it invalidates server-side tokens) or guidance on what to do after logout (e.g., re-authenticate). However, for a simple logout, it's reasonably complete, and no annotations are provided to fill the gap.

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

Parameters5/5

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

The input schema shows no parameters (empty object). The description correctly does not invent any parameter details. Since there are no parameters, no additional semantics are needed; the schema already conveys all parameter info, and the description aligns.

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?

The description clearly states the tool's purpose: logging out of Spotify by clearing OAuth tokens. It uses a specific verb ('Log out') and resource ('Spotify'), and distinguishes itself from sibling tools like spotify_auth by explicitly mentioning token clearing.

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?

It explicitly states use cases ('to reset authentication or switch accounts'), providing clear context for when to invoke. However, it does not mention when not to use it or suggest alternatives like spotify_auth for logging in, though the purpose is clear enough to infer exclusivity.

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