particle_podcast_search_transcripts instead — that one ranks segments by relevance to a free-text query, not by who’s named.
Three 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.
format="compact" (screening). The same episodes as summary, each with its mention count, the strings it was mentioned as, and the segments carrying the mentions — id, title, type, mentions in that segment, and the time of the first one — with no dialogue lines at all. Attribution is per mention line, so a mention in a segment’s opening lines is credited to that segment even though its window (which opens context_lines earlier) began in the previous one. It is the smallest shape: use it to fan out over many entities or a long date range and decide where to read. The segment ids are citations; format="detail" with the episode slug reads the lines.
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.
Output
A markdown document with## Mentions of <Name> (N episodes, format=<summary|detail|compact>) 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):
- **Mentioned as:** row and one bullet per segment carrying mentions, formatted Segment title (TYPE) — N mentions, first @ <seconds>s — segment id: <id>, in order of first mention. No dialogue is rendered. Pagination works as in summary mode.
Sample (compact, company_slug="nvidia.com", since="2026-09-10", 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.