Skip to main content
Glama
Sign In
Pipedrive MCP Server

Pipedrive MCP Server

by ckalima
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

pipedrive_create_stage

Create a new pipeline stage by providing a stage name and pipeline ID, with optional deal rotting settings.

Instructions

Create a new stage in a pipeline. name and pipeline_id are required. Use is_deal_rot_enabled and days_to_rotten to configure deal rotting.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "pipeline_id": "<pipeline_id>"
    },
    "name": "pipedrive_create_stage"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe name of the stage (required)
pipeline_idYesThe ID of the pipeline to add the stage to (required)
days_to_rottenNoDays until a deal not updated in this stage becomes rotten (applies only when is_deal_rot_enabled is set; null to clear)
deal_probabilityNoThe success probability percentage of deals in this stage (0-100)
is_deal_rot_enabledNoWhether deals in this stage can become rotten

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.7.0
    • changedInput schema / properties / days_to_rotten / description
      Previous value: -"Days until a deal not updated in this stage becomes rotten (applies only when is_deal_rot_enabled is set)"New value: +"Days until a deal not updated in this stage becomes rotten (applies only when is_deal_rot_enabled is set; null to clear)"
    • changedInput schema / properties / days_to_rotten / type
      Previous value: -"number"New value: +[
+  "number",
+  "null"
+]
  2. Addedv2.4.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description carries a lower burden. It adds that the tool creates a stage and points to deal rotting configuration, but it does not disclose any side effects, prerequisites, or further behavioral context. It adds minimal value beyond the annotations.

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 two concise sentences without filler. The purpose is front-loaded with the verb and resource, and the deal rotting note is efficiently placed. Every word earns its place.

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?

For a simple create operation with full schema coverage, the description is mostly adequate. However, it does not mention the return value (e.g., the created stage object) or any implicit prerequisites like the pipeline existing. This leaves some ambiguity for the agent.

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%, so all five parameters are fully documented. The description reiterates that name and pipeline_id are required and highlights the deal rotting parameters, but this adds little beyond what the schema already states. This meets the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Create a new stage in a pipeline' with a specific verb and resource. It also identifies required parameters. However, it does not explicitly differentiate from the sibling tool pipedrive_create_phase, though the domain difference is clear from the name.

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

Usage Guidelines3/5

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

The description mentions that name and pipeline_id are required and how to configure deal rotting, but does not provide explicit guidance on when to use this tool versus alternatives like pipedrive_update_stage. The intended usage is implied (creation), but no exclusions or alternatives are named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools