Skip to main content
Glama

Particle Report Update

particle_report_update
Destructive

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. 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.

Every member of the project's organization sees the change. Returns the updated report and its Radar link.

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": {
      "report_id": "<report_id>"
    },
    "name": "particle_report_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd of an explicit period (YYYY-MM-DD), inclusive. Requires from.
fromNoStart of an explicit period (YYYY-MM-DD). Requires to.
nameNoNew name. An empty string titles the report from its subjects.
sortNoOrder of each subject's mention list. Defaults to popularity on create.
periodNoPreset 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.
sourcesNoWhich sources the report reads. Defaults to both on create.
subjectsNoReplacement subjects, one to four, in order. Replaces the whole list; omit to leave the subjects unchanged.
report_idYesReport id to update.
episode_capNoMost episodes listed per subject (25, 50 or 100). Defaults to 25 on create.
output_formatNoOutput 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_episodesNoEpisode ids to leave out of the report's mention lists. On update, replaces the set; pass an empty list to show them all.
omitted_sectionsNoOptional 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / omitted_sections / description
      Previous value: -"Optional sections to leave out of the report. On update, replaces the set; pass an empty list to restore them all."New value: +"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."
    • changedInput schema / properties / omitted_sections / items / enum
      Previous value: -[
      -  "trend",
      -  "shared",
      -  "news"
      -]New value: +[
      +  "trend",
      +  "tone",
      +  "shared",
      +  "news",
      +  "mentions"
      +]
    • changedInput schema / properties / omitted_sections / maxItems
      Previous value: -3New value: +5
  2. Added

TDQS

A4.3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare destructiveHint=true and openWorldHint=true, so the mutation risk profile is largely covered; the description adds real value on top by stating that every member of the organization sees the change and that the update returns the report plus its Radar link. Replacement semantics for subjects, hidden_episodes and omitted_sections are disclosed, but there is no mention of permissions required or whether an update can be undone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short paragraphs, front-loaded with the verb and the mutable field set, followed by the semantics that actually bite (patch merge, list replacement, period/from-to clearing) and the visibility plus return value. No filler, no restatement of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter destructive mutation with no output schema, the definition covers what changes, what is replaced versus merged, how to clear settings (empty lists), who observes the effect, and what comes back. An agent has everything needed to invoke it correctly without opening the schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents every parameter and the baseline is 3. The description goes beyond it by explaining cross-parameter interaction ('Setting period clears an explicit from/to range, and setting from/to clears the period') and the whole-list replacement behavior of subjects, which is meaning an agent cannot safely infer from the individual field descriptions alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb (Change) and resource (a saved Radar report) and enumerates exactly which aspects are mutable: name, subjects, period, sources, sort, episode cap, omitted sections, hidden episodes. The phrase 'on create' in the field notes signals the create/update boundary against particle_report_create without needing the sibling's schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Strong in-tool guidance: 'Only the fields you pass change' establishes patch semantics, and 'subjects replaces the whole list, so pass every subject the report should keep' plus the period vs from/to exclusivity rule head off the two most likely misuse patterns. It never explicitly says when to reach for this versus particle_report_create or particle_report_get, so it stops short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources