Skip to main content
Glama

Particle Podcast Get Entity Chart

particle_podcast_get_entity_chart
Read-only

What is trending on podcasts: Particle's daily Trends charts, which rank the entities (people, shows, films, games, books, brands, athletes, teams) that the most podcasts are talking about, with each entry's movement since the previous edition and, when the editors explained it, why it moved, backed by a verbatim podcast quote and a link that plays it.

Call with no arguments for the cross-category all chart. Pick a narrower chart with chart (its schema lists every chart and the windows it publishes): entertainment (tv-series, movies, video-games), sports leagues (nfl, nba, ...), books (fiction, nonfiction, comics-manga), and guests, which ranks people by the distinct shows they appeared on. sort=acceleration surfaces the fastest risers anywhere in the chart.

Rank does not follow the podcast count: every chart except guests ranks by how far an entry's coverage sits above its own normal level, so a lower count can rank higher.

Each entry returns a slug. Pass an entity slug to particle_entity_get, or to particle_podcast_get_mention_trends (entity_slug) for which podcasts drive it; pass a person slug to particle_person_get or particle_podcast_get_guest; pass a quote's episode id to particle_podcast_get_episode.

Not for podcast shows' own chart positions on Apple or Spotify: use particle_podcast_get_rankings. Not for one subject you already know: use particle_podcast_get_mention_trends.

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

Input Schema

NameRequiredDescriptionDefault
sortNo'rank' (default): the chart as published. 'acceleration': the whole edition reordered by how fast each entry's coverage is growing, fastest first, so a fast riser deep in the chart surfaces; each entry keeps its published rank. Not measured on the guests chart, which stays in rank order.
chartNoWhich chart to read. Defaults to 'all'. The charts, with their group and the windows each publishes: 'all-entertainment': All Entertainment (entertainment; 7d) 'tv-series': TV Series (entertainment; 7d, 24h) 'movies': Movies (entertainment; 7d, 24h) 'video-games': Video Games (entertainment; 7d, 24h) 'guests': Guest Appearances (overall; 7d, 24h) 'all': All Entities (overall; 7d) 'all-sports': All Sports (sports; 7d) 'nfl': NFL (sports; 7d, 24h) 'nba': NBA (sports; 7d, 24h) 'mlb': MLB (sports; 7d, 24h) 'nhl': NHL (sports; 7d, 24h) 'college-football': College Football (sports; 7d, 24h) 'wnba': WNBA (sports; 7d) 'college-basketball': College Basketball (sports; 7d) 'soccer': Soccer (sports; 7d) 'golf': Golf (sports; 7d) 'tennis': Tennis (sports; 7d) 'formula-1': Formula 1 (sports; 7d) 'nascar': NASCAR (sports; 7d) 'pro-wrestling': Pro Wrestling (sports; 7d) 'fiction': Fiction (books; 7d) 'comics-manga': Comics & Manga (books; 7d) 'nonfiction': Non-Fiction (books; 7d)
limitNoHow many ranked entries to return, from rank 1 down (1-100, default 10).
windowNoMeasurement window. '7d' (default) ranks the last seven days; '24h' ranks the last day. The composite charts and most sports charts publish 7d only (see chart).
includeNoOptional sections. 'timeseries' adds each entry's daily podcast and mention counts. 'driven_by' names, on an entry that rises because of another entry's coverage (a song with its artist), the entry that drives it.
output_formatNoOutput serialization. 'markdown' (default) returns the LLM-facing rendering. 'json' returns the structured payload as JSON text — use only for programmatic chaining where exact field extraction matters; the JSON shape is larger and noisier for an LLM to read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover safety (readOnly/openWorld/non-destructive); the description adds genuinely non-obvious behavior: rank is driven by deviation above an entity's own baseline rather than raw podcast count, guests charts rank by distinct shows, and acceleration sort is not measured on guests. It also discloses the chaining contract (each entry returns a slug routable to entity/person/episode tools), which annotations cannot convey.

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?

Front-loads what the tool returns, then defaults, narrowing options, ranking nuance, and exclusions in a sensible order; every paragraph is functional. It runs long and the chart-group recap partially duplicates the chart enum descriptions, which is the main trim candidate.

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?

For a six-parameter, all-optional read tool with no output schema, the description covers defaults, narrowing, ranking semantics, what each entry contains (slug, movement, rationale, verbatim quote, playable link), and all sibling handoffs. An agent has everything needed to call it correctly and to route the result.

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

Parameters4/5

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

Schema description coverage is 100% and the enum descriptions already enumerate every chart and window, so the description's chart-group summary largely restates the schema. It does add meaning the schema lacks, notably that sort=acceleration surfaces fast risers anywhere in the chart and ties the slug output to specific downstream parameters (entity_slug on get_mention_trends). Modest value above a 3 baseline.

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 first sentence names the resource (Particle's daily podcast Trends charts) and the specific operation (rank entities by podcast coverage with movement and rationale), listing what an entry contains. It explicitly contrasts with two siblings by name, so an agent can distinguish it from get_rankings and get_mention_trends without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives the default invocation ('Call with no arguments for the cross-category all chart'), how to narrow (chart groups), how to reorder (sort=acceleration), and explicit negative routing: 'Not for podcast shows' own chart positions... use particle_podcast_get_rankings' and 'Not for one subject you already know: use particle_podcast_get_mention_trends.' Both alternatives are named with the condition that selects them.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources