Skip to main content
Glama

persons_create

Add a new contact to Pipedrive CRM with name, email, phone, ownership, and visibility settings.

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"}]

  • 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"} ] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesFull name of the person (required)
owner_idNoID of the user who will own this person
org_idNoID of the organization this person belongs to
emailNoEmail addresses array. Example: [{"value": "john@company.com", "primary": true, "label": "work"}]
phoneNoPhone numbers array. Example: [{"value": "+1234567890", "primary": true, "label": "mobile"}]
visible_toNoVisibility: 1 (owner only), 3 (entire company), 5 (owner's followers), 7 (visibility group)
marketing_statusNoMarketing consent status
add_timeNoCreation time in YYYY-MM-DD HH:MM:SS format
Behavior3/5

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

No annotations provided. Description discloses required and optional fields but does not discuss side effects, permissions, or validation behavior (e.g., uniqueness of names). However, for a simple create operation, the description is adequate.

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 clear sections for required and optional fields, plus a full example. Slightly verbose but overall efficient for the complexity of the parameters.

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?

No output schema, yet the description does not explain what the response contains (e.g., the created person object). However, the field descriptions and examples are comprehensive for input.

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 the description adds significant value by providing precise formats and examples for complex parameters like email and phone arrays, which are only sketched in the schema description.

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 'Create a new person in Pipedrive' with a specific verb and resource. Differentiates from sibling tools like persons_list, persons_search, and 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage from the purpose (create a person) but does not explicitly state when to use vs alternatives, nor when not to use. No exclusion criteria or prerequisites mentioned.

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/iamsamuelfraga/mcp-pipedrive'

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