Pipedrive MCP Server

pipedrive_update_person

Idempotent

Update an existing person's details in Pipedrive CRM, including contact info, organization, ownership, labels, visibility, custom fields, and marketing status.

Instructions

Update an existing person in Pipedrive.

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

Input Schema

Name	Required	Description
`id`	Yes	Person ID to update
`name`	No	New name
`emails`	No	New email addresses (array of objects)
`org_id`	No	New organization ID
`phones`	No	New phone numbers (array of objects)
`owner_id`	No	New owner user ID
`label_ids`	No	Label IDs to set on person
`visible_to`	No	New visibility: 1=Owner, 3=Group, 5=Subgroups, 7=Company
`custom_fields`	No	Custom field values as object with field keys
`marketing_status`	No	New 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": "New email addresses",
-  "items": {
-    "properties": {
-      "label": {
-        "type": "string"
-      },
-      "primary": {
-        "type": "boolean"
-      },
-      "value": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "value"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

addedInput schema / properties / emails

Added value: +{
+  "description": "New email addresses (array of objects)",
+  "items": {
+    "properties": {
+      "label": {
+        "type": "string"
+      },
+      "primary": {
+        "type": "boolean"
+      },
+      "value": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "value"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

removedInput schema / properties / phone

Removed value: -{
-  "description": "New phone numbers",
-  "items": {
-    "properties": {
-      "label": {
-        "type": "string"
-      },
-      "primary": {
-        "type": "boolean"
-      },
-      "value": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "value"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

addedInput schema / properties / phones

Added value: +{
+  "description": "New phone numbers (array of objects)",
+  "items": {
+    "properties": {
+      "label": {
+        "type": "string"
+      },
+      "primary": {
+        "type": "boolean"
+      },
+      "value": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "value"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

First observedv1.0.0Jan 30, 2026

TDQS

B3.1/5.0

Behavior3/5

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

Annotations already indicate idempotency and non-destructive behavior. The description adds no further behavioral details such as partial update semantics, response format, or required permissions.

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 at one sentence, but lacks structure or useful elaboration. Could benefit from a brief note on usage scope.

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 and no output schema, the description is insufficient. Missing details like partial vs full update, return value, and how to handle omitted fields.

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?

Input schema covers 100% of parameters with detailed descriptions. The description adds no extra meaning beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (update) and resource (existing person). However, it does not differentiate from sibling tools like pipedrive_update_person_field, which update specific aspects of a person.

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 creating a person (pipedrive_create_person) or other update tools. No prerequisites or context provided.

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

Deploy Server