Skip to main content
Glama

Report Filters

report_filters
Destructive

Replace report-level saved filter IDs or clear bindings with an empty list through a fingerprint-checked, conflict-guarded full report write that preserves other settings.

Instructions

Replace report-level saved filter IDs; [] clears this scope's bindings.

Get fingerprint and IDs from filters_list; refresh viewer before preparation. No inherit flag exists above report scope. Validates filters on their attached sources with matching draft/published. May affect eligible consumers on every page; does not change child inheritance settings. Compatibility diagnostics cover loaded report-level components only, not every child-page consumer. Full report write preserving all other settings/resources and pages, durable journal, conflict/read-back/undo guards; no publication or automatic retries.

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": {
      "filter_ids": "<filter_ids>",
      "expected_report_content_fingerprint": "<expected_report_content_fingerprint>"
    },
    "name": "report_filters"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
report_idNo
filter_idsYes
expected_report_content_fingerprintYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A4/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false and destructiveHint=true; the description goes well beyond them by disclosing that '[] clears this scope's bindings', that the write is full-report-preserving, journaled, and protected by conflict/read-back/undo guards, that it triggers no publication and no automatic retries, and that validation occurs against attached sources with matching draft/published state. This is exactly the extra behavioral context an agent needs before invoking a destructive write.

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

Conciseness3/5

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

The core action and its destructive edge case are front-loaded, which is good, but the remainder is a dense run of semicolon-joined clauses mixing prerequisites, scope limits, diagnostics coverage, and durability guarantees. No sentence is irrelevant, yet several could be split for faster scanning.

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

Completeness4/5

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

An output schema exists, so return values need no explanation, and the description covers the high-risk aspects of a destructive write: conflict guards, journaling, undo, no retries, and downstream consumer impact. The notable hole is the unmentioned dry_run parameter that defaults to a simulated run, which an agent must know about to interpret its behavior.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It explains filter_ids (replace semantics, empty-array clearing) and effectively explains expected_report_content_fingerprint as a value obtained from filters_list used for conflict guarding. However, dry_run (default true, meaning the default call is a no-op simulation) is never mentioned, and report_id is only obliquely covered by 'report-level'.

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

Purpose4/5

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

The opening sentence gives a specific verb and resource ('Replace report-level saved filter IDs') plus the scope-defining edge case ('[] clears this scope's bindings'), which separates it from page_filters and components_filters by scope. It stops short of naming an alternative tool for narrower-scope edits, so the differentiation is implied by scope wording rather than explicit.

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?

Clear preconditions are given: 'Get fingerprint and IDs from filters_list' and 'refresh viewer before preparation', plus the constraint 'No inherit flag exists above report scope'. It also sets expectations about blast radius ('May affect eligible consumers on every page') and limits diagnostics to loaded report-level components. It does not explicitly state when to prefer page_filters or components_filters instead, leaving that to inference from the scope language.

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

Deploy Server

Other Tools