Skip to main content
Glama

products_update

Update an existing product's fields in Pipedrive CRM. Provide the product ID and specify which attributes like name, price, or custom fields to modify.

Instructions

Update an existing product in Pipedrive.

All fields are optional except id. Only provide the fields you want to update.

Updatable fields:

  • name: Product name

  • code: Product code (SKU)

  • description: Product description

  • unit: Unit type

  • tax: Tax percentage

  • active_flag: Whether product is active

  • selectable: Whether product can be selected in deals

  • visible_to: Visibility level

  • owner_id: Product owner

  • prices: Array of price objects

  • billing_frequency: Billing frequency

  • billing_frequency_cycles: Number of billing cycles

Note: When updating prices, the entire prices array is replaced.

Custom fields:

  • Pass display names: { "custom_fields": { "SKU Class": "A", "Category": "Electronics" } }

  • Or hash keys directly: { "custom_fields": { "abc123...": "raw value" } }

  • For enum/set fields, pass option labels (not ids).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesProduct ID (required)
taxNoTax percentage (0-100)
codeNoProduct code/SKU
nameNoProduct name
unitNoUnit type
pricesNoArray of price objects (replaces existing prices)
owner_idNoID of the user who will own this product
selectableNoWhether product can be selected in deals
visible_toNoVisibility level
active_flagNoWhether product is active
descriptionNoProduct description
custom_fieldsNoCustom field values keyed by display name or hash.
billing_frequencyNoBilling frequency
billing_frequency_cyclesNoNumber of billing cycles
Behavior4/5

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

No annotations provided, so the description carries the full burden. It explains key behavioral traits: full replacement of prices array, optional fields, custom field handling (via display names or hash keys), and enum values for billing_frequency. Lacks mention of authorization needs, rate limits, or response structure, but given no output schema, the coverage is strong.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with sections for updatable fields, notes, and custom fields. It is moderately long but each part adds value. Could be slightly more concise by removing redundant field listing (since schema already lists them), but the clarity benefits from explicit enumeration.

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, nested objects, and no output schema, the description covers all parameters, explains custom fields and price replacement, and notes optionality. It does not describe return value or error handling, which would enhance completeness. Nevertheless, it provides sufficient context for an agent to use the tool correctly.

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%, but the description adds significant value beyond the schema by listing updatable fields in prose, explaining custom field syntax in two ways, clarifying price replacement, and providing enum options for billing_frequency. This helps an agent understand usage nuances.

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 'Update an existing product in Pipedrive' with a specific verb and resource. It lists all updatable fields, distinguishing from create and delete tools among siblings (e.g., products_create, products_delete).

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 explicitly notes that all fields except id are optional and to only provide fields to update. It also warns that the entire prices array is replaced. While it doesn't explicitly contrast with other update tools, the context from sibling names makes it clear this is for products. Could mention when to avoid updating (e.g., if creation is needed instead).

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/nubiia-dev/mcp-pipedrive'

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