Features/Changes

Add fields parameter to filter get_entity responses

1mo agoPending

I use artist.tools through the MCP connector with Claude. I am using get_entity to request information for a song, typically in batches of about 20 songs.

Right now each get_entity call also returns the full discography lists, playlist IDs, description, demographics and snapshots, so most of the response goes unused and the checks become slow and costly on the AI side.

Would it be possible to add a fields parameter to get_entity, for example fields=popularity,releasedAt,dataUpdatedAt,monthlyListeners? That alone would make each response a small fraction of its current size.

Happy to test it if you build it.

Thanks, Impulse

1 comment

  1. I like the idea of a `fields` prop.

    However, whether you just want one field or all fields, the time to resolve is identical (but it's only <50ms for an existing item, or 1-2s for an item we don't have yet).

    What I think is actually slow is how the AI is using the MCP tools, which could be an issue with our instructions/documentation the MCP offers.

    How long did it take you to get the tracks?

    I'd wonder what kind of flow it's using.

    Typically the fastest approch for the fields you want are: - use track_search tool by spotifyId (gets things instantly) - for tracks missing from that (missing from our dataset), call those eith get_entity tool

    I'd be curious if you can find more information about this so I can try to improve that.