Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

spotify_profile_followers

Retrieve public Spotify profile followers and return their profiles. Private or restricted profiles may return errors.

Instructions

Retrieve Spotify public profile followers. Returns public Spotify follower profiles. Spotify exposes this publicly for some profiles; private or restricted profiles may return an upstream error.

Input Schema

NameRequiredDescriptionDefault
uriNoSpotify user URI
urlNoopen.spotify.com user URL
limitNoFollower limit, clamped to 1-200
offsetNoFollower offset applied locally
usernameNoSpotify username

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It does add real behavioral context: it returns public follower profiles and may surface an upstream error for private/restricted profiles. It does not mention pagination behavior, rate limits, or the read-only nature, leaving gaps for a no-annotation 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?

Three short sentences with the core purpose front-loaded and no filler. Slightly repetitive ('public profile followers' then 'public Spotify follower profiles'), which keeps it from a 5.

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?

For a 5-parameter read tool with no annotations and no output schema, the description covers purpose, return type, and an error mode but omits pagination semantics and how the identity parameters interact. Adequate but with clear gaps.

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% (uri, url, username, limit, offset all documented), so the schema does the heavy lifting. The description adds no parameter-level meaning such as how the three identity inputs (uri/url/username) relate or which is preferred, so the 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?

States a specific verb and resource: 'Retrieve Spotify public profile followers.' An agent can tell this is about a profile's follower list, distinct from spotify_profile (profile details) and spotify_profile_playlists. It does not explicitly name any sibling, so it stays just short of a 5.

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 implied by the resource, and the note about private/restricted profiles partially guides the agent on when this will succeed. However, there is no explicit when-to-use or when-not-to-use framing, and no named alternative for related needs (e.g., profile details or playlists).

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