particle_podcast_search_transcripts instead — that one ranks segments by relevance to a free-text query, not by who’s named.
Two response modes
format="summary" (default — wide scan). Returns up to limit episodes (reverse-chronological), each with metadata plus the first 10 mention-only lines (just the lines naming the entity, no surrounding dialogue). Use this to see what’s been said across episodes and decide which episodes are worth reading in full. Paginate older episodes with cursor.
format="detail" (narrow drill-in). Requires episode_slug. Returns the full mention windows with context_lines of surrounding dialogue around each mention. Pass one slug for a single episode, or up to 10 comma-separated slugs (e.g. episode_slug="all-in-200,all-in-201,all-in-202") to multi-get several episodes in one call. limit/cursor don’t apply.
Workflow
- No specific episode in mind: call
format="summary"first to scan, then callformat="detail"with the slug(s) of the episodes worth reading in full. For most questions (sentiment, recurring themes, who said what when), summary alone has enough signal and the second call isn’t needed. - Already have the episode slug (e.g. user mentioned the episode by name, or you got it from
particle_podcast_get_episode/particle_podcast_search_transcripts): skip summary entirely and callformat="detail"withepisode_slugdirectly.
Inputs
One ofperson_slug or company_slug is required. Resolve a name to a slug first with particle_person_resolve, particle_entity_resolve, or particle_company_resolve.
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
format | "summary" | "detail" | no | "summary" | Response shape. See “Two response modes” above. |
person_slug | string | one of | — | Person slug from particle_person_resolve or particle_entity_resolve (e.g. "sam-altman"). Also accepts a bare entity slug for non-person entities like places. |
company_slug | string | one of | — | Company slug, domain, or canonical ID (e.g. "nvidia" or "nvidia.com"). Resolves to the company’s linked entity. |
episode_slug | string | yes for detail | — | One slug for single drill-in, or up to 10 comma-separated slugs for a multi-episode drill-in in one call. In summary mode, optional filter to one episode. |
podcast_slug | string | no | — | Restrict mentions to a single podcast by slug, ID, or numeric iTunes ID. |
role | enum | no | — | Constrain how the entity participates. One of: guest, host, panelist, correspondent, mention. |
since | string | no | — | Only episodes published on or after this ISO 8601 date (e.g. 2025-01-01). |
until | string | no | — | Only episodes published on or before this ISO 8601 date. |
context_lines | integer (1–20) | no | 2 | Surrounding dialogue lines around each mention. Detail mode only — ignored in summary. |
limit | integer (1–50) | no | 10 | Episodes per page. Summary mode only. |
cursor | string | no | — | Opaque pagination cursor. Summary mode only. |
Output
A markdown document with## Mentions of <Name> (N episodes, format=<summary|detail>) and one ### Episode title section per episode. Each section carries bulleted KV rows: - **Podcast:**, - **Podcast slug:**, - **Published:**, - **Episode slug:**, - **Mentions:**.
In summary mode, each episode is followed by a flat bullet list — one bullet per mention, formatted @ <seconds>s **Speaker:** text. When more pages exist, a horizontal rule and a **Cursor:** <value> line are appended; pass that value back as cursor to fetch the next page.
In detail mode, each episode is followed by one bullet per mention window (Segment title (TYPE) @ start–end), then indented dialogue lines underneath. The line that actually names the entity has the entire Speaker: text wrapped in bold; surrounding context lines render as **Speaker:** text (speaker label bold, text plain).
Sample (summary, person_slug="marc-andreessen", limit=2):
Example
Related
- REST equivalent:
GET /v1/podcasts/mentions. - For ranked dialogue about a topic (not just lines naming a person), use
particle_podcast_search_transcripts. - For episode-level discovery without dialogue, use
particle_podcast_list_episodes.