Skip to main content
Glama

filters_delete

Delete a filter permanently from Pipedrive. Use with a filter ID to remove unused filters.

Instructions

Delete a filter in Pipedrive.

Marks a filter as deleted. The filter will no longer be available for use.

Workflow tips:

  • Use filters/list to find filter IDs to delete

  • Use filters/get to verify filter details before deletion

  • For deleting multiple filters at once, use filters/bulk_delete instead

  • Deletion is permanent and cannot be undone

Common use cases:

  • Delete a specific filter: { "id": 123 }

  • Remove unused filter: { "id": 456 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the filter to delete (required)
Behavior5/5

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

With no annotations, the description fully handles behavioral transparency. It states deletion is permanent and cannot be undone, and that the filter will no longer be available. No contradictions.

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 separate sections for description, workflow tips, and common use cases. Every sentence adds value with no redundancy.

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

Completeness5/5

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

For a simple delete operation with one parameter and no output schema, the description covers effect, prerequisites, and provides examples. It is fully sufficient for correct invocation.

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?

Only one parameter (id) with 100% schema coverage. Description adds examples of common use cases (e.g., delete filter with id 123), but these are not essential beyond the schema. Baseline 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?

Clearly states the tool deletes a filter in Pipedrive. The description specifies the resource (filter) and action (delete), and distinguishes from filters/bulk_delete for deletion of multiple filters.

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

Usage Guidelines5/5

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

Provides explicit workflow tips: use filters/list to find IDs, filters/get to verify, and notes filters/bulk_delete for multiple deletions. Also includes common use cases, which guide the agent on when to use this tool.

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