Skip to main content
Glama

leads_create

Create a lead in Pipedrive linked to a person or organization. Requires a title; supports optional 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".

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)
owner_idNoID of the user who will own this lead
label_idsNoArray of label UUIDs
person_idNoID of the person this lead is associated with
organization_idNoID of the organization this lead is associated with
valueNoLead value with amount and currency
expected_close_dateNoExpected close date in YYYY-MM-DD format
visible_toNoVisibility: 1=Owner, 3=Owner's group, 5=Owner's group and sub-groups, 7=Entire company
was_seenNoWhether the lead was seen
origin_idNoOrigin ID for tracking
channelNoChannel ID
channel_idNoChannel identifier string
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It mentions that API-created leads have source_name 'API' and origin 'API', and that leads inherit custom fields from deals. However, it does not describe the response format, permissions, or error conditions.

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?

The description is well-structured with separate sections and front-loaded with the purpose. It is informative but slightly verbose; some sentences could be condensed.

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 the complexity (12 parameters, nested objects, no output schema), the description covers key aspects: required fields, dependencies, formatting, and usage patterns. Missing output specification is a minor gap.

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 value by explaining the relationship between person_id and organization_id, providing formatting tips (date format, UUIDs for label_ids), and giving concrete examples.

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 explains that a lead must be linked to a person or organization. It distinguishes from sibling tools like leads_update or leads_get by focusing on creation.

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 requirements (title, person_id/organization_id). Does not explicitly list when not to use, but the context is clear.

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