Pipedrive MCP Server

pipedrive_search_organizations

Read-onlyIdempotent

Search Pipedrive organizations by name or address. Filter by fields, use exact match, and paginate results.

Instructions

Search for organizations by name or address.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "term": "<term>"
    },
    "name": "pipedrive_search_organizations"
  }
}

Input Schema

Name	Required	Description
`term`	Yes	Search term
`limit`	No	Number of results (1-100)
`cursor`	No	Cursor for pagination (from previous response)
`fields`	No	Comma-separated fields to search (name, address, notes, custom_fields). Defaults to all.
`exact_match`	No	Use exact match

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv2.4.0Jun 17, 2026

addedInput schema / properties / cursor

Added value: +{
+  "description": "Cursor for pagination (from previous response)",
+  "type": "string"
+}

addedInput schema / properties / fields

Added value: +{
+  "description": "Comma-separated fields to search (name, address, notes, custom_fields). Defaults to all.",
+  "type": "string"
+}

First observedv1.0.0Jan 30, 2026

TDQS

B3.3/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds no additional behavioral context, such as pagination behavior or field search behavior, beyond what is in the schema.

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?

One concise sentence with no wasted words. Could be slightly expanded to include key behavior like pagination without losing conciseness.

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?

No output schema is provided, and the description does not explain the return structure, pagination with cursor, or that it returns a list. Given 5 parameters and no output schema, it is incomplete.

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 description coverage is 100%, so the schema already documents all parameters. The description adds minimal value by mentioning 'name or address' which maps to the 'fields' parameter.

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 the verb 'search' and the resource 'organizations', and specifies the search criteria 'by name or address'. This distinguishes it from sibling search tools for deals, leads, etc.

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

Usage Guidelines3/5

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

The description implies usage for searching organizations, but no explicit guidance on when to use or not use this tool versus alternatives like pipedrive_get_organization or pipedrive_list_organizations.

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

Deploy Server