Skip to main content
Glama

filters_bulk_delete

Delete multiple Pipedrive filters in one operation by providing comma-separated IDs. Streamlines cleanup of unused or outdated filters.

Instructions

Delete multiple filters at once in Pipedrive.

Marks multiple filters as deleted in a single operation. More efficient than deleting one at a time.

Workflow tips:

  • Provide comma-separated filter IDs as a string (e.g., "1,2,3,4")

  • Use filters/list to find filter IDs to delete

  • All specified filters will be deleted in one API call

  • Deletion is permanent and cannot be undone

Common use cases:

  • Delete multiple filters: { "ids": "123,456,789" }

  • Clean up old filters: { "ids": "1,2,3,4,5" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYesComma-separated filter IDs to delete (required). Example: "1,2,3"
Behavior4/5

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

No annotations provided, so description carries full burden. It clearly states deletion is permanent and cannot be undone, and that all specified filters are deleted in one call. Lacks details on error handling (e.g., invalid IDs) or side effects.

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?

Well-structured with concise sections: purpose, efficiency, workflow tips, common use cases. No wasted words, front-loaded key information.

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?

For a simple bulk delete tool with one parameter and no output schema, description covers purpose, usage, and permanence. Missing details on error handling or return values, but complete enough for typical use.

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%, baseline 3. Description adds value by specifying format (comma-separated string), providing examples, and common use cases, going beyond the schema's basic description.

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 clearly states it deletes multiple filters at once, using specific verb 'delete' and resource 'multiple filters'. It distinguishes from the sibling tool 'filters_delete' by highlighting bulk operation and efficiency.

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?

Provides explicit workflow tips, including when to use (bulk delete for efficiency) and how to get filter IDs via filters/list. However, it does not explicitly mention when not to use, such as for single filter deletion (use filters_delete instead).

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/iamsamuelfraga/mcp-pipedrive'

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