Skip to main content
Glama

filters_create

Create a new filter in Pipedrive to organize deals, organizations, people, products, or activities. Define conditions with operators to segment your CRM data.

Instructions

Create a new filter in Pipedrive.

Adds a new filter with conditions. Returns the filter ID upon success.

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/helpers to discover available field IDs and operators

  • Structure: { glue: "and", conditions: [{ glue: "and", conditions: [...] }, { glue: "or", conditions: [...] }] }

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

  • Filter types: deals, org, people, products, activities

Example simple filter: { "name": "High value deals", "type": "deals", "conditions": { "glue": "and", "conditions": [ { "glue": "and", "conditions": [ { "object": "deal", "field_id": "value", "operator": ">", "value": 10000 } ] }, { "glue": "or", "conditions": [null] } ] } }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesFilter name (required)
typeYesFilter type (required)
conditionsYesFilter conditions structure with glue and conditions array (required)
Behavior4/5

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

No annotations provided, so description carries full burden. Discloses important limitations: only one first-level condition group, two second-level groups, max 16 conditions, required glue constraints. Mentions return value (filter ID).

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 clear sections (limitations, workflow tips, example). Front-loaded with main action. Length is justified by complexity; no unnecessary sentences.

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?

Comprehensive for a creation tool with nested conditions. Covers all structural constraints, provides example, references external tools for discovery. No output schema but return value noted.

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 100%, description adds significant value by explaining the conditions structure, providing an example, listing common operators and filter types, and referencing helpers for field IDs.

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?

Clear verb 'Create' with specific resource 'new filter in Pipedrive'. Distinguishes from sibling tools like filters_get, filters_list, filters_update by focusing on creation. Returns filter ID.

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 workflow tips referencing filters/helpers for field discovery, lists permitted filter types and operators, and outlines limitations. Does not explicitly state when not to use, but offers sufficient contextual guidance.

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