Skip to main content
Glama

Pipedrive

by io.github.pipeworx-io

Pipedrive Search

pipedrive_search
Read-onlyIdempotent

Search deals, contacts, organizations, products, or files by keyword. Returns matching records with IDs and basic info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesSearch term
limitNoMax results (default 50)
_apiKeyYesPipedrive API token
item_typesNoComma-separated item types to search: deal, person, organization, product, file (default: all)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoSearch results grouped by item type
successNoWhether the request succeeded

Schema Changelog

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

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Search results grouped by item type",
+      "properties": {
+        "deals": {
+          "description": "Matching deals",
+          "items": {
+            "properties": {
+              "id": {
+                "description": "Deal ID",
+                "type": "number"
+              },
+              "title": {
+                "description": "Deal title",
+                "type": "string"
+              },
+              "value": {
+                "description": "Deal value",
+                "type": "number"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "files": {
+          "description": "Matching files",
+          "items": {
+            "properties": {
+              "id": {
+                "description": "File ID",
+                "type": "number"
+              },
+              "name": {
+                "description": "File name",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "organizations": {
+          "description": "Matching organizations",
+          "items": {
+            "properties": {
+              "id": {
+                "description": "Organization ID",
+                "type": "number"
+              },
+              "name": {
+                "description": "Organization name",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "persons": {
+          "description": "Matching contacts",
+          "items": {
+            "properties": {
+              "email": {
+                "description": "Email address",
+                "type": "string"
+              },
+              "id": {
+                "description": "Contact ID",
+                "type": "number"
+              },
+              "name": {
+                "description": "Contact name",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "products": {
+          "description": "Matching products",
+          "items": {
+            "properties": {
+              "id": {
+                "description": "Product ID",
+                "type": "number"
+              },
+              "name": {
+                "description": "Product name",
+                "type": "string"
+              }
+            },
+            "type": "object"
+          },
+          "type": "array"
+        }
+      },
+      "type": "object"
+    },
+    "success": {
+      "description": "Whether the request succeeded",
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-pipedrive-api-key",
+    "term": "Acme Corp"
+  },
+  {
+    "_apiKey": "your-pipedrive-api-key",
+    "item_types": "person,deal",
+    "term": "John Smith"
+  }
+]
  3. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is well-covered. The description adds that results include IDs and basic info, but does not disclose additional behaviors like pagination, default limits, or rate limits. This is acceptable for a simple read-only search tool but not particularly rich.

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?

The description is a single, efficient sentence that front-loads the core purpose and return value. No unnecessary words or repetition.

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 search tool with full schema coverage, rich annotations, and an output schema, the description covers the essential purpose and return information. The schema handles parameter details, and annotations handle safety, making this complete.

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?

The input schema provides full descriptions for all four parameters, so the description does not need to compensate. The description adds no extra parameter semantics beyond what the schema already provides, so a baseline score of 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?

The description clearly states the tool performs a keyword search across multiple Pipedrive entity types (deals, contacts, organizations, products, files) and returns records with IDs and basic info. This distinguishes it from sibling get/list tools which operate on single entities or list all.

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?

The description makes it clear that this is for keyword-based searching across specified entity types, implying it is appropriate when you need to find records by term rather than fetching by known ID or listing all. However, it does not explicitly state when not to use it or mention alternatives like pipedrive_get_deal or pipedrive_list_deals.

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

All Pipedrive toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

Multiple tools have overlapping purposes, e.g., ask_pipeworx and ask_pipeworx_grounded are nearly identical, and entity_profile, compare_entities, and deep_research all perform multi-source lookups. An agent would struggle to distinguish between them.

Naming Consistency2/5

Naming conventions are highly inconsistent, mixing snake_case (ask_pipeworx), lowercase (deep_research), and prefixed patterns (pipedrive_, polymarket_, pipeworx_). No unified verb_noun pattern exists across the set.

Tool Count2/5

With 35 tools, the count is too high for a server named Pipedrive, which suggests a CRM focus. Many tools are unrelated to CRM (e.g., prediction market, weather, economic data), making the surface feel bloated and unfocused.

Completeness3/5

The Pipedrive subset lacks create/update/delete operations, leaving basic CRUD incomplete. However, the broader data lookup tools cover a wide range of domains (financials, drugs, patents), so overall coverage is moderate but not fully coherent with the server name.

Resources