Skip to main content
Glama

delete-viz-filters-bulk

Delete multiple visualization filters by providing an array of filter IDs, removing them all in one request.

Instructions

Delete multiple visualization filters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filter_idsYesArray of filter IDs to delete.
Behavior2/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It merely states the action ('delete multiple filters') without mentioning irreversibility, partial-failure handling, permissions, or side effects. This is a significant gap for a destructive operation.

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?

The description is a single, tightly worded sentence that effectively conveys the tool's purpose. There is no filler or redundancy, and the key information is front-loaded.

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

Completeness2/5

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

This is a simple bulk-delete tool with one parameter and no output schema or annotations, but the description is still under-specified. It does not mention return values, max batch size, error behavior (e.g., rollback vs. skip), or any prerequisites. More context is needed for an agent to use it confidently.

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 coverage is 100% (the single parameter 'filter_ids' has a clear description: 'Array of filter IDs to delete.'). The tool description adds no additional parameter meaning, but since the schema already fully documents it, the baseline score of 3 is appropriate.

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?

The description uses a specific verb ('delete') with a clear resource ('visualization filters') and explicitly notes the bulk scope ('multiple'). This distinguishes it from its sibling tool 'delete-viz-filter' (singular), making the purpose unambiguous.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives, such as the singular 'delete-viz-filter' or other bulk operations. The name 'bulk' hints at the context, but the description does not explain when this tool is preferred or any exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ibm-client-engineering/concert-operate-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server