> ## Documentation Index
> Fetch the complete documentation index at: https://docs.particle.pro/llms.txt
> Use this file to discover all available pages before exploring further.

# particle_report_update

> Rename a saved Radar report, replace its subjects, or change its settings.

Change a saved Radar report: rename it, replace its subjects, or change its period, sources, sort, episode cap, omitted sections or hidden episodes. Only the fields you pass change. Every member of the project's organization sees the change.

* `subjects` replaces the whole list, so pass every subject the report should keep.
* Setting `period` clears an explicit `from`/`to` range, and setting `from`/`to` clears the period.
* `omitted_sections` and `hidden_episodes` replace their sets; an empty list clears one.
* An empty `name` titles the report from its subjects again.

## Inputs

| Field | Type | Required | Description |
| - | - | - | - |
| `report_id` | string | yes | Report id to update. |
| `name` | string | no | New name, up to 120 characters. |
| `subjects` | array | no | Replacement subjects, one to four, shaped as on [`particle_report_create`](https://docs.particle.pro/mcp/tools/reports/report-create#inputs). |
| `period`, `from`, `to`, `sources`, `sort`, `episode_cap`, `omitted_sections`, `hidden_episodes` | — | no | As on [`particle_report_create`](https://docs.particle.pro/mcp/tools/reports/report-create#inputs), without the defaults: an omitted field keeps its stored value. |

## Output

The updated report, in the same markdown as [`particle_report_create`](https://docs.particle.pro/mcp/tools/reports/report-create#output).

## Example

```text theme={"dark"}
Agent calls: particle_report_update {
  "report_id": "5Hq2VbKc8mR1tW9y",
  "period": "30d",
  "sources": ["podcasts"]
}
```

## Related

* REST equivalent: `PATCH /v1/reports/{id}`.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.