Skip to main content
Glama

Particle Report Create

particle_report_create

Save 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

NameRequiredDescriptionDefault
toNoEnd of an explicit period (YYYY-MM-DD), inclusive. Requires from.
fromNoStart of an explicit period (YYYY-MM-DD). Requires to.
nameNoReport name. Omit to title the report from its subjects ("A vs B").
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.
subjectsYesOne to four subjects, in the order the report compares them.
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.8/5.0
Behavior5/5

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

Beyond the annotations (readOnly=false, openWorld=true, destructive=false) it discloses the permission model ("Every member of the project's organization can open and edit it"), the side effect that the output is a link to a page rather than returned data, and the create-time defaults for period and sources. That is materially useful context an agent could not infer from the annotation flags alone.

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

Conciseness4/5

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

Front-loaded with the outcome and return value, then prerequisites, then use/avoid guidance — a sensible ordering. It is slightly longer than needed, with some overlap between the first sentence's page description and the later "a report is a page to open, not data returned to you", but no sentence is filler.

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 an 11-parameter creation tool with no output schema, the description covers what an agent needs: what gets created, how to source the subject identifiers, what happens by default, what is returned, who can access it, and which tools consume the id. Nothing decision-relevant is missing.

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 a baseline of 3 applies, and the description goes beyond it by explaining the entity/keyword relationship ("Resolve each person, company or topic first ... and pass the slug as `entity`; use `keyword` for a name with no slug") plus the defaults for period and sources. It does not explain `sort`, `episode_cap`, `hidden_episodes` or `omitted_sections`, which are left entirely to the schema.

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?

Opens with a concrete verb and resource ("Save a Radar report in your project") and defines exactly what the artifact is: a page comparing one to four subjects with podcast mentions over time plus news coverage. It also states the return value (report id and Radar link), so an agent knows both what it creates and what it gets back without opening the schema.

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

Usage Guidelines5/5

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

Explicitly states when to use it ("when the user asks for a report, or to compare or share coverage") and when not to, naming the alternative family: "To answer a question about coverage now, use the podcast tools instead: a report is a page to open, not data returned to you." It also routes the agent upstream to particle_entity_resolve/particle_person_resolve/particle_company_resolve and downstream to particle_report_get/update/delete via the returned id.

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