Skip to main content
Glama
NovaLux12

SpotifyMCP

by NovaLux12
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

verify_receipt

Read-onlyIdempotent

Confirm whether a previous Spotify change took effect by looking up its session-scoped receipt ID; an unknown or expired ID means the lookup failed, not the change.

Instructions

Verify that a previous mutation actually landed on Spotify by looking up its receipt. Receipts are session-scoped: the 100 most recent mutations, in this process only, and lost on restart unless SPOTIFY_MCP_RECEIPTS is set. An unknown or expired id returns isError with found:false — a fact about the lookup, not about the mutation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
receipt_idYesReceipt ID copied verbatim from a receipt-bearing mutation result (rcpt_<bootId>-<n>)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv3.0.1
    • changedInput schema / properties / receipt_id / description
      Previous value: -"Receipt ID from a receipt-bearing mutation result"New value: +"Receipt ID copied verbatim from a receipt-bearing mutation result (rcpt_<bootId>-<n>)"
    • removedInput schema / properties / receipt_id / minLength
      Removed value: -1
    • addedInput schema / properties / receipt_id / pattern
      Added value: +"^rcpt_(?:[0-9a-z]+-)?\\d+$"
  2. Changed2 schema fields changedv1.31.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  3. Addedv1.26.1

TDQS

A4.3/5.0
Behavior5/5

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

Adds substantial context beyond the readOnly/idempotent annotations: session-scoped retention (100 most recent, this process only, lost on restart unless SPOTIFY_MCP_RECEIPTS is set) and precise error semantics (isError with found:false is a fact about the lookup, not the mutation). This is exactly the operational detail annotations cannot carry.

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?

Three tight sentences, front-loaded with the core action, then retention semantics, then error meaning. Every sentence carries non-redundant information; nothing is padding.

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

Completeness5/5

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

With no output schema, the description supplies the return contract (isError with found:false) and the retention window, which are the facts an agent needs to interpret results correctly. Nothing material is missing.

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%: the pattern and the 'rcpt_<bootId>-<n>' format are already documented in the schema. The description reinforces the id's origin ('copied verbatim from a receipt-bearing mutation result') but adds no format or syntax beyond that.

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?

States a specific verb and resource: verifying that a prior mutation landed, by looking up its receipt. The operation is unambiguous and distinct from mutating siblings. It stops short of naming the nearest alternatives (undo_mutation, undo_last_mutation), so an agent must infer the boundary itself.

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?

Clearly frames the use case: confirm that a previous mutation actually landed on Spotify. It also explains the provenance of the input ('receipt-bearing mutation result'), which tells the agent when this tool is applicable. No explicit when-not-to-use or named alternative is provided.

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