Skip to main content
Glama

leads_update

Update an existing lead's properties, including title, value, custom fields, or archive status. Send null to clear optional fields.

Instructions

Update an existing lead in Pipedrive.

Updates one or more properties of a lead. Only properties included in the request will be updated. Send null to unset a property (applicable for value, person_id, or organization_id).

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:

  • Only include fields you want to update

  • Lead ID must be a UUID

  • Use null to clear optional fields

  • value must be an object with amount and currency

  • Leads inherit custom fields structure from deals

  • Set is_archived to true to archive a lead

Common use cases:

  • Update title: { "id": "", "title": "Updated Title" }

  • Update value: { "id": "", "value": { "amount": 10000, "currency": "USD" } }

  • Archive lead: { "id": "", "is_archived": true }

  • Clear person: { "id": "", "person_id": null }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesUUID of the lead to update (required)
titleNoLead title
valueNoLead value with amount and currency (null to clear)
channelNoChannel ID
owner_idNoID of the user who will own this lead
was_seenNoWhether the lead was seen
label_idsNoArray of label UUIDs
person_idNoID of the person associated with this lead (null to clear)
channel_idNoChannel identifier string
visible_toNoVisibility level
is_archivedNoWhether the lead is archived
custom_fieldsNoCustom field values keyed by display name or hash. Uses deal field definitions.
organization_idNoID of the organization associated with this lead (null to clear)
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?

No annotations are provided, so the description must fully convey behavioral traits. It explains partial update semantics, null clearing behavior, custom field handling, and lead-deal custom field inheritance. However, it does not describe the return value or error behavior, which is a gap for a mutation tool with 14 parameters.

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 relatively long but well-structured with sections: main purpose, custom field notes, workflow tips, and common use cases. It is front-loaded with the verb+resource statement. While informative, it could be slightly more concise without losing key details.

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?

Given no output schema and no annotations, the description should provide a complete picture. It covers update behavior, custom fields, and usage tips, but omits information about the response (e.g., whether it returns the updated lead object). For a complex tool with 14 parameters, this missing return value context reduces completeness.

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 description coverage is 100%, so the schema already documents parameters. The description adds value by explaining null behavior, custom field formats (display names vs. hash keys), and workflow tips like 'Lead ID must be a UUID' and 'value must be an object with amount and currency.' This extra context goes beyond the schema.

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 the tool's purpose: 'Update an existing lead in Pipedrive.' It distinguishes from sibling tools like leads_create and leads_delete by specifying it is for updating existing leads, and provides multiple concrete use cases (title update, value update, archive, clear person).

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?

The description provides workflow tips and common use cases that guide the agent on when to use this tool. It explains which fields to include, how to clear optional fields, and gives examples. However, it does not explicitly mention alternatives or when not to use it (e.g., for bulk updates, but no bulk update sibling exists).

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