Skip to main content
Glama

pipelines_create

Create a new sales pipeline in Pipedrive. Specify required name and optional order, active status, and deal probability settings.

Instructions

Create a new pipeline.

Creates a new pipeline with the specified name and configuration.

Workflow tips:

  • Only name is required

  • Set order_nr to control display order (lower numbers first)

  • active=false to create inactive pipeline

  • deal_probability=true enables probability tracking (default)

  • New pipelines start with no stages - add stages separately

Common use cases:

  • Simple pipeline: { "name": "Sales Pipeline" }

  • Inactive pipeline: { "name": "Archive", "active": false }

  • Ordered pipeline: { "name": "Q1 Pipeline", "order_nr": 1 }

  • Full config: { "name": "Enterprise Sales", "order_nr": 2, "active": true, "deal_probability": true }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesPipeline name (required, max 255 chars)
order_nrNoOrder number for display
activeNoWhether pipeline is active
deal_probabilityNoEnable deal probability tracking
Behavior4/5

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

No annotations are provided, so the description bears full responsibility. It discloses that new pipelines start with no stages and need stages added separately, which is useful behavioral context beyond a simple 'create'.

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 a main line, workflow tips, and common use cases. It is concise, front-loaded with purpose, and each section adds value without redundancy.

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?

The description covers parameter usage and behavioral notes well, but lacks information about return values or response structure. Given no output schema, this omission leaves the AI agent without guidance on what to expect.

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?

Schema coverage is 100%, so the schema already describes parameters. The description adds value with usage examples and tips (e.g., 'active=false to create inactive pipeline'), enriching the meaning beyond the 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 pipeline' with a specific verb and resource. Among sibling tools (pipelines_get, pipelines_update, etc.), it is distinct and unambiguous.

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 provides workflow tips and common use cases, guiding which parameters to use for different scenarios. However, it does not explicitly mention when not to use this tool or compare to alternatives like updating an existing pipeline.

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