Skip to main content
Glama
comma-compliance

pipedrive-mcp

by comma-compliance
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Remote

pipedrive_persons_update

Update an existing Pipedrive person by ID, including names, emails, phones, owner, visibility, labels, and custom fields by name or API key.

Instructions

Update an existing person. Supports custom fields by name or key, and the native Label field via label_ids (IDs or label names).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
emailsNo
org_idNo
phonesNo
owner_idNoUser ID of the owner
label_idsNoNative Label field. Label option IDs or label names (e.g. [367] or ['Test / Internal']). Replaces existing labels; pass [] to clear. Sent as top-level label_ids, not a custom field.
person_idYesThe person ID to update
visible_toNoVisibility: 1=owner only, 3=owner's group, 5=owner's group+sub, 7=everyone
custom_fieldsNoCustom fields by API key (e.g. { 'abc123hash': 'value' })
custom_fields_by_nameNoCustom fields by human-readable name (e.g. { 'Tier': 'Enterprise' })

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.1.1
    • addedInput schema / properties / custom_fields / description
      Added value: +"Custom fields by API key (e.g. { 'abc123hash': 'value' })"
    • addedInput schema / properties / custom_fields_by_name / description
      Added value: +"Custom fields by human-readable name (e.g. { 'Tier': 'Enterprise' })"
    • addedInput schema / properties / label_ids
      Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "anyOf": [
+          {
+            "type": "integer"
+          },
+          {
+            "type": "string"
+          }
+        ]
+      },
+      "type": "array"
+    },
+    {
+      "type": "integer"
+    },
+    {
+      "type": "string"
+    }
+  ],
+  "description": "Native Label field. Label option IDs or label names (e.g. [367] or ['Test / Internal']). Replaces existing labels; pass [] to clear. Sent as top-level label_ids, not a custom field."
+}
    • addedInput schema / properties / owner_id / description
      Added value: +"User ID of the owner"
    • addedInput schema / properties / visible_to / description
      Added value: +"Visibility: 1=owner only, 3=owner's group, 5=owner's group+sub, 7=everyone"
  2. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden for a mutation tool. It hints that custom fields can be supplied by name or key and that labels go through label_ids, but says nothing about partial-update semantics (what happens to unspecified fields), required permissions, reversibility, or side effects.

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?

Two tight sentences with the core operation front-loaded and the capability note following. No padding, though it could be slightly more informative without adding length.

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?

For a 10-parameter mutation tool with nested objects, no annotations, and no output schema, the description is thin. It leaves partial-update behavior, auth requirements, and most parameter meanings unaddressed, so an agent lacks what it needs to invoke this safely and correctly.

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 description coverage is 60%, and the description adds real meaning for two params: custom_fields/custom_fields_by_name (by name or key) and label_ids (IDs or label names). However, several params (name, emails, org_id, phones) have no schema descriptions and are not compensated for in the description.

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?

States a clear verb+resource ('Update an existing person') and adds scope about custom fields and the native Label field. It does not differentiate itself from siblings like pipedrive_persons_merge or pipedrive_persons_create, but the operation is unambiguous.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g. needing a valid person_id), and no routing to alternatives such as merge or create. 'Update an existing person' implies context but provides no explicit usage conditions or exclusions.

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

Deploy Server

Other Tools