Skip to main content
Glama

Pipedrive

by io.github.pipeworx-io

Pipedrive List Persons

pipedrive_list_persons
Read-onlyIdempotent

View all contacts in your CRM. Returns names, email addresses, phone numbers, and associated organizations and deals.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results (max 500, default 50)
startNoPagination start (default 0)
_apiKeyYesPipedrive API token

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoList of contacts
successNoWhether the request succeeded
additional_dataNoPagination and metadata

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": {
+    "additional_data": {
+      "description": "Pagination and metadata",
+      "type": "object"
+    },
+    "data": {
+      "description": "List of contacts",
+      "items": {
+        "properties": {
+          "email": {
+            "description": "Email addresses",
+            "items": {
+              "properties": {
+                "value": {
+                  "description": "Email address",
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "id": {
+            "description": "Contact ID",
+            "type": "number"
+          },
+          "name": {
+            "description": "Contact name",
+            "type": "string"
+          },
+          "org_id": {
+            "description": "Associated organization ID",
+            "type": "number"
+          },
+          "phone": {
+            "description": "Phone numbers",
+            "items": {
+              "properties": {
+                "value": {
+                  "description": "Phone number",
+                  "type": "string"
+                }
+              },
+              "type": "object"
+            },
+            "type": "array"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "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"
+  },
+  {
+    "_apiKey": "your-pipedrive-api-key",
+    "limit": 100
+  }
+]
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds value by specifying the returned data (emails, phones, associated organizations/deals), which helps the agent set expectations without contradicting 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?

The description is two sentences long, with the primary action stated in the first sentence and return fields in the second. Every word earns its place; there is no fluff or redundancy.

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 the tool's low complexity, strong annotations (read-only, idempotent, destructive=false), and the presence of an output schema, the description fully covers the necessary context. It even previews the return fields, making the tool self-sufficient for an agent.

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 has 100% description coverage for all three parameters (limit, start, _apiKey), so the schema fully explains parameter meaning. The description adds no additional parameter semantics beyond what the schema already provides, so baseline 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 uses a specific verb ('View all contacts') and identifies the resource (contacts in CRM), clearly distinguishing it from siblings like pipedrive_get_person (specific person) and pipedrive_list_deals (deals). It also lists expected output fields, making the tool's purpose unambiguous.

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 provides clear context for when to use this tool: to view all contacts in the CRM. It does not explicitly name alternatives or exclusions, but the sibling tool names and the description's focus make the usage scenario obvious.

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