Skip to main content
Glama

deals_create

Add a deal to Pipedrive with a required title, and optionally set value, currency, associated person or organization, pipeline stage, custom fields, and expected close date.

Instructions

Create a new deal in Pipedrive.

Creates a new deal with the specified information. Only title is required.

Custom fields:

  • Pass display names: { "custom_fields": { "Industria": "Tech", "Budget": 5000 } }

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

  • For enum/set fields, pass option labels (not ids).

Workflow tips:

  • Title is the only required field

  • Use persons/search or organizations/search to get person_id or org_id

  • Use pipelines/list to get pipeline_id and stage_id

  • Set expected_close_date in YYYY-MM-DD format

  • Probability should be 0-100 (percentage)

  • Currency must be a 3-letter code (e.g., USD, EUR, GBP)

Common use cases:

  • Simple deal: { "title": "New Deal", "value": 5000, "currency": "USD" }

  • Deal with person: { "title": "Deal", "value": 1000, "person_id": 123 }

  • Deal with organization: { "title": "Deal", "org_id": 456, "stage_id": 1 }

  • Full deal: { "title": "Big Deal", "value": 50000, "currency": "USD", "person_id": 123, "org_id": 456, "pipeline_id": 1, "stage_id": 2, "expected_close_date": "2024-12-31" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesDeal title (required)
valueNoDeal value
org_idNoID of the organization this deal is associated with
statusNoDeal status (default: open)
user_idNoID of the user who will own this deal
add_timeNoCreation time in ISO 8601 format
currencyNo3-letter currency code (e.g., USD, EUR)
stage_idNoID of the stage this deal will be in
person_idNoID of the person this deal is associated with
visible_toNoVisibility: 1=Owner, 3=Owner's group, 5=Owner's group and sub-groups, 7=Entire company
lost_reasonNoReason why the deal was lost
pipeline_idNoID of the pipeline this deal will be in
probabilityNoDeal success probability (0-100)
custom_fieldsNoCustom field values keyed by display name or hash. See description for format.
expected_close_dateNoExpected close date in YYYY-MM-DD format
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only describes creation parameters and does not mention side effects, permissions, rate limits, or any behavioral traits beyond the act of creating.

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 sections (Custom fields, Workflow tips, Common use cases) and is mostly efficient. However, it is somewhat lengthy and could be slightly more concise without losing clarity.

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?

Given 15 parameters, only 1 required, no output schema, the description is exceptionally complete. It covers all parameters, provides format hints (dates, currency, probability), and gives multiple example payloads for common scenarios.

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?

Schema coverage is 100%, and the description adds significant value by explaining custom fields (with both display names and hash keys), enum/set fields (use labels), and providing full examples. It greatly enhances understanding beyond the bare 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 'Create a new deal in Pipedrive' and elaborates on what it does. It distinguishes from sibling tools like deals_update or deals_merge by focusing solely 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?

The description includes workflow tips and common use cases, guiding when to use the tool. It references related tools (persons/search, organizations/search, pipelines/list) to get required IDs, but does not explicitly state when not to use it.

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