Skip to main content
Glama

products_update

Update an existing product's details including name, code, description, pricing, billing, and visibility settings in Pipedrive.

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.

Input Schema

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

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

No annotations are provided, so the description must cover behavioral traits. It notes that updating prices replaces the entire array, but lacks details on permissions, side effects, idempotency, or error conditions. Adequate but not thorough.

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 concise and well-structured: a clear purpose, a usage guideline, a bulleted field list, and a special note. Every sentence serves a purpose without unnecessary words.

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?

The description covers the purpose, list of updatable fields, and a critical behavior note. However, it omits return value information and error handling, which would be helpful given the tool's complexity (13 parameters).

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 coverage is 100% with parameter descriptions. The description repeats these and adds a note about price replacement. It adds slight value beyond the schema, but not significantly.

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 it from sibling tools like products_create or 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 provides clear context: 'All fields are optional except id. Only provide the fields you want to update.' This guides usage, but does not explicitly mention when not to use this tool or suggest alternatives among siblings.

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