Particle Report Create
particle_report_createSave a Radar report in your project: a page comparing one to four people, companies, topics or keywords side by side, with their podcast mentions over time, every mention linked to the minute, and their news coverage. Returns the report's id and its Radar link; give the user the link, since the page is where the report is read (and downloaded as a PDF). Every member of the project's organization can open and edit it.
Resolve each person, company or topic first with particle_entity_resolve, particle_person_resolve or particle_company_resolve and pass the slug as entity; use keyword for a name with no slug. The period defaults to the last three months and the sources to podcasts and news.
Use it when the user asks for a report, or to compare or share coverage. To answer a question about coverage now, use the podcast tools instead: a report is a page to open, not data returned to you. The id feeds particle_report_get, particle_report_update and particle_report_delete.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"subjects": "<subjects>"
},
"name": "particle_report_create"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | End of an explicit period (YYYY-MM-DD), inclusive. Requires from. | |
| from | No | Start of an explicit period (YYYY-MM-DD). Requires to. | |
| name | No | Report name. Omit to title the report from its subjects ("A vs B"). | |
| sort | No | Order of each subject's mention list. Defaults to popularity on create. | |
| period | No | Preset period: a number of days or months back (e.g. 30d, 3mo, 12mo) or all. Set this or from/to, not both. Defaults to 3mo on create. | |
| sources | No | Which sources the report reads. Defaults to both on create. | |
| subjects | Yes | One to four subjects, in the order the report compares them. | |
| episode_cap | No | Most episodes listed per subject (25, 50 or 100). Defaults to 25 on create. | |
| output_format | No | Output 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. | |
| hidden_episodes | No | Episode ids to leave out of the report's mention lists. On update, replaces the set; pass an empty list to show them all. | |
| omitted_sections | No | Optional sections to leave out of the report: trend, tone, shared (shows in common), news, or mentions (every subject's mention list). On update, replaces the set; pass an empty list to restore them all. |