particle_podcast_get_entity_chart

Particle’s daily Trends charts rank the entities that the most podcasts are talking about: people, TV series, films, games, books, brands, athletes, and teams. Each entry carries its movement since the previous edition. When the editors explained an entry, it also carries why it moved, backed by a verbatim podcast quote and a link that plays it. Call the tool with no arguments for the cross-category all chart. Pick a narrower chart with chart:

Overall: all (every subject), guests (people ranked by the distinct shows they appeared on).
Entertainment: all-entertainment, tv-series, movies, video-games.
Sports: all-sports and one chart per league or sport, such as nfl, nba, soccer, golf, formula-1.
Books: fiction, nonfiction, comics-manga.

The chart input schema lists every chart with its group and the windows it publishes, so the list above can lag behind it. Use the schema, or particle_catalog, as the source of truth. Each entry returns a slug. Pass an entity slug to particle_entity_get, or to particle_podcast_get_mention_trends as entity_slug to see 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 the chart positions of podcast shows on Apple Podcasts or Spotify: use particle_podcast_get_rankings. Not for one subject you already know: use particle_podcast_get_mention_trends. Rank does not always follow the podcast count. Most charts weigh how far an entry’s coverage sits above its own normal level, so a lower count can rank higher. Entity charts describes how each chart ranks.

Inputs

Field	Type	Required	Default	Description
`chart`	string	no	`all`	Which chart to read. One of the registered chart slugs; the schema enum lists them.
`window`	string	no	`7d`	`7d` or `24h`. The composite charts and most sports charts publish `7d` only, and a `24h` call to one of them is refused with the window it does publish.
`limit`	integer (1–100)	no	10	How many entries to return, from rank 1 down.
`sort`	string	no	`rank`	`rank` returns the chart as published. `acceleration` reorders the whole edition by how fast each entry’s coverage is growing, so a fast riser deep in the chart comes first; each entry keeps its published rank. The `guests` chart stays in rank order.
`include`	string[]	no	—	`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_format`	string	no	`markdown`	`json` returns the same shape as `GET /v1/podcasts/entities/charts/{category}`.

Output

A markdown document headed ## Trends: <chart> (<window>, edition YYYY-MM-DD), then one ### block per entry:

### <rank>. <name> (<movement>), where movement is up N, down N, new, or no change.
**Entity slug:** or **Person slug:**.
**Momentum:** with the breaking badge and the momentum state (rising, steady, settling, cooling, new), when the chart measures one.
**Podcasts:** (on guests, **Shows appeared on:**) and **Mentions:**, each with the previous window’s count.
**Acceleration:** when the entry has a baseline.
Facts such as **Network:**, **Developer:**, or **Publisher:**.
**Why:**, the quote as a blockquote, **Source:** with the show, episode, and episode id, and **Listen:** with a link that plays the quote. The quote and its receipt appear only when the source episode still exists.
On guests: up to three recent appearances and the guest’s **Highlight clip:**.
**Note:** when a caveat applies, for example when a release or news spike has passed and the drop is not a real decline.

When the edition’s explanations are still being written, a line under the header says so. Sample (chart=tv-series, limit=1):

## Trends: TV Series (7d, edition 2026-10-28)

### 1. Severance (up 3)
**Entity slug:** severance
**Momentum:** breaking
**Podcasts:** 41 (previous window 12)
**Mentions:** 130 (previous window 30)
**Acceleration:** 2.4x its six-day baseline
**Network:** Apple TV+
**Why:** The season finale aired.
> That finale broke me.
**Source:** The Watch, Finale recap (episode id 7Kq2...)
**Listen:** https://radar.particle.pro/podcasts/the-watch/episodes/finale-recap?t=61

Example

What is trending on podcasts this week:

Agent calls: particle_podcast_get_entity_chart {}

The fastest-rising NFL players and teams today, with their daily history:

Agent calls: particle_podcast_get_entity_chart {
  "chart": "nfl",
  "window": "24h",
  "sort": "acceleration",
  "include": ["timeseries"]
}

REST equivalent: GET /v1/podcasts/entities/charts/{category}. GET /v1/podcasts/entities/charts lists every chart with its rank-1 entry.
For guests making the rounds over 30 days, with expertise filters, use particle_podcast_list_guests with mode: "trends".

Get started

Tools

particle_podcast_get_entity_chart

Inputs

Output

Example

​Inputs

​Output

​Example

​Related

Inputs

Output

Example

Related