Skip to main content
Glama

persons_create

Create a person record in Pipedrive by providing a name and optional fields for contact information, organization, visibility, and custom fields.

Instructions

Create a new person in Pipedrive.

Required fields:

  • name: Full name of the person

Optional fields:

  • 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)

  • add_time: Optional creation time in YYYY-MM-DD HH:MM:SS format

Example email/phone arrays: { "email": [ {"value": "john@company.com", "primary": true, "label": "work"}, {"value": "john@personal.com", "primary": false, "label": "home"} ], "phone": [ {"value": "+1234567890", "primary": true, "label": "mobile"} ] }

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
nameYesFull name of the person (required)
emailNoEmail addresses array. Example: [{"value": "john@company.com", "primary": true, "label": "work"}]
phoneNoPhone numbers array. Example: [{"value": "+1234567890", "primary": true, "label": "mobile"}]
org_idNoID of the organization this person belongs to
add_timeNoCreation time in YYYY-MM-DD HH:MM:SS format
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 exist, so description carries burden. It discloses that this creates a person but lacks info on idempotency, validation, or side effects. Examples for complex fields help.

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, though somewhat lengthy. Includes examples and details but remains clear. Could be more concise.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, description covers all parameters with examples and custom field handling. Lacks response details but is adequate for a creation tool.

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 has 100% coverage with descriptions. Description adds value by providing detailed examples for email/phone arrays, custom_fields, and explanations for enums like visible_to and marketing_status.

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 clearly states 'Create a new person in Pipedrive.' and lists required and optional fields. It is distinct from sibling tools like persons_update or persons_delete.

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 vs alternatives, such as checking for duplicates with persons_search before creation. Only field details are provided.

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