Skip to main content
Glama

leads_delete

Permanently delete a lead from Pipedrive by its UUID. Use this action to remove leads that are no longer needed, noting that deletion is irreversible.

Instructions

Delete a specific lead from Pipedrive.

Permanently deletes a lead by its UUID. This action cannot be undone.

Workflow tips:

  • Lead ID must be a UUID

  • This permanently deletes the lead

  • Consider archiving instead (use leads/update with is_archived: true)

  • Returns the deleted lead's ID on success

Common use cases:

  • Delete a lead: { "id": "adf21080-0e10-11eb-879b-05d71fb426ec" }

Alternative:

  • Archive instead of delete: Use leads/update with { "id": "", "is_archived": true }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesUUID of the lead to delete
Behavior4/5

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

Discloses permanent deletion, irreversibility, and return value. No annotations provided, so description carries full burden; lacks auth/rate limit info but acceptable for simple delete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Concise yet comprehensive: clear sections (description, workflow tips, common use cases, alternative). No fluff.

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

Completeness5/5

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

For a single-parameter delete tool with no output schema, description covers behavior, usage, and alternatives completely.

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?

Input schema already documents 'id' with description. Description reinforces UUID format and provides example, adding value beyond 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?

Clearly states 'Delete a specific lead' with emphasis on permanence. Distinct from sibling leads_update which offers archiving.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly advises when to use (delete) vs when to archive (alternative via leads_update). Includes UUID requirement and irreversible nature.

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