Skip to main content
Glama

leads_create

Create a new lead in Pipedrive by providing a title and linking to a person or organization. Optionally add deal value, expected close date, and custom fields.

Instructions

Create a new lead in Pipedrive.

Creates a new lead with the specified information. A lead must be linked to a person or an organization (or both). All leads created through the API will have source_name "API" and origin "API".

Custom fields:

  • Pass display names: { "custom_fields": { "Source": "Web", "Budget": 5000 } }

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

  • Uses deal field definitions (leads share the deal custom fields).

Workflow tips:

  • Title is required

  • Must have person_id, organization_id, or both

  • Use persons/search or organizations/search to get IDs

  • Value is optional but recommended (object with amount and currency)

  • Leads inherit custom fields structure from deals

  • Set expected_close_date in YYYY-MM-DD format

  • label_ids is an array of UUID strings

Common use cases:

  • Simple lead: { "title": "New Lead", "person_id": 123 }

  • Lead with value: { "title": "Lead", "person_id": 123, "value": { "amount": 5000, "currency": "USD" } }

  • Lead with org: { "title": "Company Lead", "organization_id": 456 }

  • Full lead: { "title": "Big Lead", "person_id": 123, "organization_id": 456, "value": { "amount": 50000, "currency": "USD" }, "expected_close_date": "2024-12-31", "owner_id": 1 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesLead title (required)
valueNoLead value with amount and currency
channelNoChannel ID
owner_idNoID of the user who will own this lead
was_seenNoWhether the lead was seen
label_idsNoArray of label UUIDs
origin_idNoOrigin ID for tracking
person_idNoID of the person this lead is associated with
channel_idNoChannel identifier string
visible_toNoVisibility: 1=Owner, 3=Owner's group, 5=Owner's group and sub-groups, 7=Entire company
custom_fieldsNoCustom field values keyed by display name or hash. Uses deal field definitions.
organization_idNoID of the organization this lead is associated with
expected_close_dateNoExpected close date in YYYY-MM-DD format
Behavior3/5

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

Discloses that leads created via API have source_name 'API' and origin 'API', and that leads share deal custom fields. No annotations are provided, so missing details on rate limits or auth, but reasonable for a create tool.

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-organized with sections: description, custom fields, workflow tips, and common use cases. Slightly verbose but structured for clarity.

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?

Covers essential aspects for a complex create tool with 13 parameters (nested objects). Explains required associations, custom fields, date format, and visibility. Missing output details but acceptable without output schema.

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

Parameters5/5

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

Adds significant value beyond the input schema, e.g., explaining custom fields can use display names or hashes, example payloads, date format, label_ids as UUIDs, and visible_to enum values. Schema coverage is 100%, but the description enriches understanding.

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 lead in Pipedrive' and specifies that a lead must be linked to a person or organization. It distinguishes from sibling tools like leads_update and deals_create.

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 workflow tips and common use cases, including required parameters and ID lookup hints. However, it does not explicitly contrast with other creation tools like deals_create, but the context is clear since leads and deals are distinct.

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