Pipedrive MCP Server

pipedrive_create_person

Create a new Pipedrive person (contact) using only a name; add optional emails, phones, and organizational data.

Instructions

Create a new person (contact) in Pipedrive. Only name is required.

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": {
      "name": "<name>"
    },
    "name": "pipedrive_create_person"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Person name (required)
`emails`	No	Email addresses (array of objects, e.g. [{ value, primary, label }])
`org_id`	No	Organization ID to link to
`phones`	No	Phone numbers (array of objects, e.g. [{ value, primary, label }])
`add_time`	No	Creation time (RFC3339 format) - backdate the person
`owner_id`	No	Owner user ID
`label_ids`	No	Label IDs to attach to person
`visible_to`	No	Visibility: 1=Owner, 3=Group, 5=Subgroups, 7=Company
`custom_fields`	No	Custom field values as object with field keys
`marketing_status`	No	Marketing status

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv2.4.0Jun 17, 2026

removedInput schema / properties / email

Removed value: -{
-  "description": "Email addresses",
-  "items": {
-    "properties": {
-      "label": {
-        "description": "Label (work, home, other)",
-        "type": "string"
-      },
-      "primary": {
-        "description": "Is primary email",
-        "type": "boolean"
-      },
-      "value": {
-        "description": "Email address",
-        "type": "string"
-      }
-    },
-    "required": [
-      "value"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

addedInput schema / properties / emails

Added value: +{
+  "description": "Email addresses (array of objects, e.g. [{ value, primary, label }])",
+  "items": {
+    "properties": {
+      "label": {
+        "description": "Label (work, home, other)",
+        "type": "string"
+      },
+      "primary": {
+        "description": "Is primary email",
+        "type": "boolean"
+      },
+      "value": {
+        "description": "Email address",
+        "type": "string"
+      }
+    },
+    "required": [
+      "value"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

removedInput schema / properties / phone

Removed value: -{
-  "description": "Phone numbers",
-  "items": {
-    "properties": {
-      "label": {
-        "description": "Label (work, home, mobile)",
-        "type": "string"
-      },
-      "primary": {
-        "description": "Is primary phone",
-        "type": "boolean"
-      },
-      "value": {
-        "description": "Phone number",
-        "type": "string"
-      }
-    },
-    "required": [
-      "value"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

addedInput schema / properties / phones

Added value: +{
+  "description": "Phone numbers (array of objects, e.g. [{ value, primary, label }])",
+  "items": {
+    "properties": {
+      "label": {
+        "description": "Label (work, home, mobile)",
+        "type": "string"
+      },
+      "primary": {
+        "description": "Is primary phone",
+        "type": "boolean"
+      },
+      "value": {
+        "description": "Phone number",
+        "type": "string"
+      }
+    },
+    "required": [
+      "value"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

First observedv1.0.0Jan 30, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already indicate non-readonly, non-destructive, non-idempotent, and open world. The description adds the constraint that only name is required, which is useful but already implied by the schema. No additional behavioral details like side effects or limitations.

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?

Extremely concise with two sentences, front-loading the action. Could potentially add more detail without becoming verbose, but it's efficient.

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?

With 10 parameters, nested objects, and no output schema, the description is too brief. It does not explain return values, error handling, or what happens on success. The agent may need more context to correctly interpret the tool's behavior.

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 coverage is 100%, so all parameters are described in the schema. The description reinforces that name is required, which matches the schema's required field. No new semantic meaning beyond what the schema provides.

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?

Clearly states the tool creates a new person/contact in Pipedrive with a specific verb and resource. Differentiates from sibling tools like create_deal or update_person.

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?

Mentions that only name is required, but does not provide explicit guidance on when to use this tool versus alternatives (e.g., creating an organization or lead). No when-not scenarios or competitor tools mentioned.

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

Deploy Server