Skip to main content
Glama
ckalima

Pipedrive MCP Server

pipedrive_create_deal

Create a new deal in Pipedrive. Only title is required, but you can optionally add value, currency, owner, person, organization, pipeline, stage, status, close date, probability, visibility, labels, and custom fields.

Instructions

Create a new deal in Pipedrive. Only title is required; all other fields are optional.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesDeal title (required)
valueNoDeal monetary value
currencyNo3-letter currency code (e.g., USD, EUR)
owner_idNoOwner user ID
person_idNoID of person to link to deal
org_idNoID of organization to link to deal
pipeline_idNoPipeline ID
stage_idNoStage ID
statusNoDeal status
expected_close_dateNoExpected close date (YYYY-MM-DD)
probabilityNoSuccess probability (0-100)
visible_toNoVisibility: 1=Owner, 3=Group, 5=Subgroups, 7=Company
label_idsNoLabel IDs to attach to deal
custom_fieldsNoCustom field values as object with field keys
Behavior3/5

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

Annotations already provide readOnlyHint=false, destructiveHint=false, etc. Description adds that only title is required, but does not disclose side effects, permissions, or response behavior. With annotations present, minimal additional value.

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?

Single sentence that is front-loaded with the tool's purpose and key constraint. No wasted words.

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?

Tool has 14 parameters with 100% schema coverage but no output schema. The description does not mention return value, typical usage, or prerequisites. For a create tool with many optional fields, more context on behavior after creation would be helpful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with detailed parameter descriptions. The description only reiterates the required field, adding no new semantic info. Baseline 3 appropriate.

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?

Description clearly states 'Create a new deal in Pipedrive' with a specific verb and resource. It also distinguishes from sibling tools like pipedrive_update_deal by focusing on creation. The requirement of only title is highlighted.

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?

Description indicates when to use (creating a deal) and notes that only title is required, but lacks explicit when-not-to-use or alternatives. However, sibling tools imply clear distinctions.

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/ckalima/pipedrive-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server