Skip to main content
Glama

deals_create

Create a new deal in Pipedrive CRM. Provide at least a title; optionally add value, associated person or organization, pipeline stage, and expected close date.

Instructions

Create a new deal in Pipedrive.

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

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
currencyNo3-letter currency code (e.g., USD, EUR)
user_idNoID of the user who will own this deal
person_idNoID of the person this deal is associated with
org_idNoID of the organization this deal is associated with
pipeline_idNoID of the pipeline this deal will be in
stage_idNoID of the stage this deal will be in
statusNoDeal status (default: open)
expected_close_dateNoExpected close date in YYYY-MM-DD format
probabilityNoDeal success probability (0-100)
lost_reasonNoReason why the deal was lost
visible_toNoVisibility: 1=Owner, 3=Owner's group, 5=Owner's group and sub-groups, 7=Entire company
add_timeNoCreation time in ISO 8601 format
Behavior4/5

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

With no annotations, the description carries full burden. It discloses validations (enum values, date format, probability range) and required fields, but does not mention potential side effects like notifications or permission requirements. Still highly transparent.

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?

The description is well-structured with clear sections, concise sentences, and front-loaded purpose. Every sentence adds value, with no redundancy.

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 14 parameters and no output schema, the description is very complete. It covers required fields, constraints, and common usage patterns. However, it does not mention what the response contains (e.g., deal ID), which is a minor gap.

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%, but the description adds significant value with examples, format hints, and workflow integration (e.g., using persons/search). It clarifies semantic meaning beyond the schema for each parameter.

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: 'Create a new deal in Pipedrive.' It specifies that only title is required and provides examples and workflow tips, effectively differentiating it from siblings like deals_update or deals_search.

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?

The description includes explicit workflow tips on how to obtain related IDs (persons, organizations, pipelines) and provides common use cases with example JSON payloads, guiding the agent on when and how to use the tool effectively.

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