Skip to main content
Glama

filters_update

Update an existing filter's name and conditions in Pipedrive. Modify filter properties directly without recreating.

Instructions

Update an existing filter in Pipedrive.

Updates a filter's name and/or conditions. Only provide fields you want to change.

IMPORTANT LIMITATIONS:

  • Only ONE first-level condition group is supported (must be glued with 'AND')

  • Only TWO second-level condition groups are supported

  • First second-level group must be glued with 'AND'

  • Second second-level group must be glued with 'OR'

  • Maximum of 16 conditions per filter

Workflow tips:

  • Use filters/get to see current filter configuration before updating

  • Use filters/helpers to discover available field IDs and operators

  • Can update name only, conditions only, or both

  • Common operators: =, !=, <, >, <=, >=, LIKE, IN, IS NULL, IS NOT NULL

Common use cases:

  • Rename filter: { "id": 123, "name": "New Name" }

  • Update conditions: { "id": 123, "conditions": {...} }

  • Update both: { "id": 123, "name": "Updated", "conditions": {...} }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the filter to update (required)
nameNoNew filter name (optional)
conditionsNoNew filter conditions structure (optional)
Behavior4/5

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

With no annotations, description carries burden. Details important limitations: condition group structure, max conditions. Notes that only provided fields change. Missing authentication/rate limits, but acceptable for an update tool.

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?

Well-structured with sections, front-loaded purpose. Slightly verbose, but justified by complexity and examples.

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?

Given complexity of conditions, description is thorough: limitations, workflow tips, examples. No output schema, but update tools typically return updated object; not needed.

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 covers 100% of parameters. Description adds value: explains conditions structure, common operators, examples. More than baseline needed.

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 'Update an existing filter in Pipedrive.' Specifies the resource (filter) and action (update). Distinguishes from siblings by focusing on update vs create/delete.

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?

Gives explicit when to use: updating filter name/conditions. Provides workflow tips (use filters/get, filters/helpers) and lists limitations. Does not state when not to use, but context is clear.

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