Skip to main content
Glama
ckalima

Pipedrive MCP Server

by ckalima
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

pipedrive_search_deals

Read-onlyIdempotent

Search deals by title text with fuzzy or exact match, filter by status, organization, or person, and paginate through results.

Instructions

Search for deals by text in title. Supports fuzzy matching by default.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesSearch term
limitNoNumber of results (1-100)
cursorNoCursor for pagination (from previous response)
fieldsNoComma-separated fields to search (title, notes, custom_fields). Defaults to all.
org_idNoFilter by linked organization
statusNoFilter by status (omit to return all non-deleted deals)
person_idNoFilter by linked person
exact_matchNoUse exact match instead of fuzzy

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changedv2.4.0
    • 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 (title, notes, custom_fields). Defaults to all.",
+  "type": "string"
+}
    • changedInput schema / properties / status / description
      Previous value: -"Filter by status"New value: +"Filter by status (omit to return all non-deleted deals)"
    • changedInput schema / properties / status / enum
      Previous value: -[
-  "open",
-  "won",
-  "lost",
-  "deleted",
-  "all_not_deleted"
-]New value: +[
+  "open",
+  "won",
+  "lost",
+  "deleted"
+]
  2. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already indicate read-only, non-destructive, idempotent, and open-world behavior. The description adds the key behavioral detail of fuzzy matching by default, which is beyond the annotations.

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?

Two sentences, no wasted words, front-loaded with the core action. Every sentence contributes meaning.

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

Completeness3/5

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

Despite 100% schema coverage and good annotations, the description does not mention pagination, the optional fields parameter, or return behavior. For a complex search tool with 8 parameters, this leaves some gaps.

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 has 100% parameter descriptions, so the baseline is 3. The description adds no extra semantic value beyond the schema's existing parameter docs.

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', the resource 'deals', and the constraint 'by text in title'. It also notes default fuzzy matching, distinguishing it from other search tools for different entities (e.g., pipedrive_search_leads).

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like pipedrive_list_deals or other search tools. No explicit conditions, exclusions, or context for selection.

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

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