Crawlora MCP

spotify_profile_followers

Read-only

Fetch public Spotify follower-profile records for a profile username, uri, or url, paginated by limit/offset. Private or restricted profiles may return an upstream error. Use spotify_profile_playlists for public playlists or spotify_profiles_search to find profiles.

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_profile_followers"
  }
}

Input Schema

Name	Required	Description
`uri`	No	Spotify user URI, e.g. spotify:user:spotify; provide one of username, uri, or url.
`url`	No	Open Spotify user URL, e.g. https://open.spotify.com/user/spotify; provide one of username, uri, or url.
`limit`	No	Follower limit, clamped to 1-200.
`offset`	No	Follower offset, default 0.
`username`	No	Spotify username, e.g. spotify; provide one of username, uri, or url.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety/network profile is covered. The description adds genuinely useful behavioral context beyond that: only public follower-profile records are returned, private/restricted profiles can yield an upstream error, and results are paginated via limit/offset.

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 front-loaded sentences with no filler: purpose/identifiers first, failure mode second, sibling routing last. Slightly awkward phrasing ('follower-profile records') costs a point but structure is efficient.

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?

With an output schema present, return values need no elaboration, and annotations cover the safety profile. The description fills the key gaps (identifier forms, pagination, error case, alternatives), leaving only minor ambiguity about what 'follower-profile records' contain.

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%, so the schema already documents the identifier options and limit/offset clamping. The description restates the identifier choices and pagination but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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 (Fetch) and resource (public Spotify follower-profile records) with the accepted identifier forms (username/uri/url). It explicitly names sibling tools it is not (spotify_profile_playlists, spotify_profiles_search), so an agent can route without opening schemas.

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 names two alternatives with their conditions: 'Use spotify_profile_playlists for public playlists or spotify_profiles_search to find profiles.' That covers when to reach for siblings, but it never states the positive trigger for this tool (e.g., 'use when you need a profile's follower list') beyond the implied purpose.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.