Skip to main content
Glama

persons_update

Update a person's record in Pipedrive CRM with new name, email, phone, job title, or custom fields using the person ID.

Instructions

Update an existing person's information.

Required fields:

  • id: Person ID to update

Optional fields (only provide fields you want to change):

  • name: Full name

  • owner_id: User who will own this person

  • org_id: Organization this person belongs to

  • email: Array of email addresses with format: [{"value": "john@company.com", "primary": true, "label": "work"}]

  • phone: Array of phone numbers with format: [{"value": "+1234567890", "primary": true, "label": "mobile"}]

  • job_title: Job title / function of the person (max 255 characters)

  • visible_to: Visibility level (1=owner only, 3=entire company, 5=owner's followers, 7=visibility group)

  • marketing_status: Marketing consent status (no_consent, unsubscribed, subscribed, archived)

Note: When updating email/phone arrays, provide the complete array (it replaces the existing one).

Custom fields:

  • Pass display names: { "custom_fields": { "Region": "EU", "Tier": "Gold" } }

  • Or hash keys directly: { "custom_fields": { "abc123...": "raw value" } }

  • For enum/set fields, pass option labels (not ids).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesPerson ID to update
nameNoFull name of the person
emailNoEmail addresses array (replaces existing). Example: [{"value": "john@company.com", "primary": true, "label": "work"}]
phoneNoPhone numbers array (replaces existing). Example: [{"value": "+1234567890", "primary": true, "label": "mobile"}]
org_idNoID of the organization this person belongs to
owner_idNoID of the user who will own this person
job_titleNoJob title / function of the person (max 255 characters)
visible_toNoVisibility: 1 (owner only), 3 (entire company), 5 (owner's followers), 7 (visibility group)
custom_fieldsNoCustom field values keyed by display name or hash.
marketing_statusNoMarketing consent status
Behavior3/5

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

No annotations provided, so description bears full burden. Discloses array replacement behavior and custom field options. Lacks information on error handling, permissions, or return value. Adequate but not comprehensive.

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?

Well-structured with sections for required, optional, notes, and custom fields. Every sentence adds value, though slightly verbose. Efficiently organized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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, description covers usage well but omits return value and error conditions. Adequate for an update tool but could be more complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds valuable context: explains replacement for email/phone arrays and two ways to pass custom fields. Additional info beyond schema merits a higher score.

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 'Update an existing person's information' with specific verb and resource. Lists required and optional fields, distinguishing it from create/get/delete siblings.

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?

Provides clear guidance: requires id, only provide fields to change, and notes that email/phone arrays replace existing. Does not explicitly state when not to use or mention alternatives like persons_create but is implicit.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nubiia-dev/mcp-pipedrive'

If you have feedback or need assistance with the MCP directory API, please join our Discord server