Retrieve all filter groups defined in a QuickSight analysis by providing its analysis ID, so you can review or manage the filters applied to your data.
List all filter groups defined in a QuickSight analysis.
| Name | Required | Description | Default |
|---|---|---|---|
| analysis_id | Yes | The QuickSight analysis ID. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint=true annotation already establishes this is a safe, non-mutating read, so the description need not repeat that. However, it adds no behavioral context of its own — no note on pagination, ordering, or whether the list is complete for nested/linked analyses. A minimal but acceptable contribution given annotation coverage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One front-loaded sentence with the verb and scope stated immediately and no filler. It is efficient, though slightly under-powered for a tool with an output schema whose contents go unmentioned.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter read tool with full schema coverage and an existing output schema, the description supplies what the agent needs to invoke it correctly. The only mild gap is not noting how the returned filter groups relate to the add/delete filter group siblings.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There is a single required parameter and schema description coverage is 100%, with the schema already stating 'The QuickSight analysis ID.' The description adds no format, sourcing, or lookup guidance beyond that, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('List') and resource ('filter groups') scoped to a QuickSight analysis, which is enough to distinguish it from add_filter_group and delete_filter_group. It is clear but does not explicitly name what it is not, and 'filters' vs 'filter groups' could be briefly ambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No indication of when to use this rather than sibling read tools such as get_parameters or describe_analysis, and no prerequisites or exclusions. The agent must infer usage entirely from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.