Skip to main content
Glama

Page Filters

page_filters
Destructive

Set page-local saved filter IDs and inheritance from report scope with fingerprint-guarded writes, preview and undo, without rewriting child settings.

Instructions

Set page-local saved filter IDs and/or inheritance from report scope.

change.filter_ids replaces the complete list ([] clears); inherit_filters changes inheritance independently; omitted/null properties stay unchanged. Native validation uses each filter's attached source with matching draft and published schema. Preview consumer compatibility is advisory: incompatible consumers may ignore inherited filters, and a compatible one may disable inheritance. Does not rewrite child settings or runtime control selections. Refresh viewer first, use page_get and filters_list fingerprints. One guarded page write/read-back/undo; no automatic publication or cross-entity transaction.

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": {
      "page_id": "<page_id>",
      "change": "<change>",
      "expected_page_fingerprint": "<expected_page_fingerprint>",
      "expected_report_content_fingerprint": "<expected_report_content_fingerprint>"
    },
    "name": "page_filters"
  }
}

Input Schema

NameRequiredDescriptionDefault
changeYes
dry_runNo
page_idYes
report_idNo
expected_page_fingerprintYes
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?

With annotations only marking this destructive/non-read-only, the description carries the rest: list replacement semantics, null-means-unchanged behavior, validation source rules, advisory preview compatibility, and the guarded write/read-back/undo with no automatic publication or cross-entity transaction. That is substantial disclosure beyond the annotation flags.

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?

Mutation semantics are front-loaded and no sentence is filler, but the second half becomes telegraphic fragments ('Change ... omitted/null properties stay unchanged') whose grammar takes a second read. Still appropriately sized for a destructive six-parameter write.

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?

Covers the risky behavior (what is replaced, what is untouched, validation, no publication, guarded undo) for a destructive nested-object mutation, and an output schema exists so return shape needn't be described. The unmentioned dry_run default is the main completeness gap.

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 0%, so the description must compensate: it explains change.filter_ids replacement (including [] clearing) and inherit_filters independence, and points to page_get/filters_list for fingerprints. It does not explain the dry_run flag (default true) or the expected_* fingerprint mismatch behavior, leaving those to schema names alone.

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?

States a specific verb and resource: setting page-local saved filter IDs and/or inheritance from report scope. It is distinguishable from page_filter_inheritance only by its narrower scope phrasing ('inheritance independently'), not by explicit contrast with that sibling.

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

Usage Guidelines3/5

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

Gives sequencing advice ('Refresh viewer first, use page_get and filters_list fingerprints') and a preview-compatibility caveat, which implies prerequisites. It never says when to prefer page_filter_inheritance or report_filters instead, so alternative selection is left to inference.

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