Skip to main content
Glama

pipelines_update

Modify a pipeline's details including name, order, active status, and probability tracking in Pipedrive.

Instructions

Update an existing pipeline.

Updates pipeline configuration including name, order, active status, and probability tracking.

Workflow tips:

  • All fields except id are optional

  • Use order_nr to reorder pipelines

  • Set active=false to deactivate pipeline

  • Changing deal_probability affects all stages

  • At least one field should be updated

Common use cases:

  • Rename pipeline: { "id": 1, "name": "New Sales Pipeline" }

  • Deactivate pipeline: { "id": 1, "active": false }

  • Reorder pipeline: { "id": 1, "order_nr": 5 }

  • Update multiple fields: { "id": 1, "name": "Updated", "active": true, "order_nr": 1 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the pipeline to update
nameNoNew pipeline name (max 255 chars)
order_nrNoNew order number
activeNoWhether pipeline is active
deal_probabilityNoEnable/disable probability tracking
Behavior3/5

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

With no annotations, the description bears full burden. It discloses a side effect (changing deal_probability affects all stages) and states that at least one field must be updated. However, it does not discuss permissions, rate limits, or consequences of deactivating a pipeline.

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 succinct and well-structured: a clear opening sentence, bullet-pointed workflow tips, and illustrative examples. Every sentence contributes meaning without 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?

Covers key aspects for an update tool: what fields can be changed, constraints, and usage patterns. However, it lacks information about the return value (e.g., the updated pipeline object), which would improve completeness given no output schema.

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?

Input schema has 100% coverage; description adds value via common use case examples and clarifies that all fields except id are optional. This enhances understanding beyond the schema alone, though not extensively.

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 it updates an existing pipeline and lists the configurable fields (name, order, active status, probability tracking). It uses specific verbs and resource, making the tool's purpose 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?

Provides workflow tips (all fields optional except id, order_nr reordering, active=false deactivation, deal_probability affects all stages) and common use cases with examples. However, it does not explicitly state when to avoid this tool or compare to alternatives like pipelines_create.

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