Skip to main content
Glama
ckalima

Pipedrive MCP Server

pipedrive_update_product

Idempotent

Update an existing product's details including name, code, prices, and custom fields in Pipedrive.

Instructions

Update an existing product in Pipedrive.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesProduct ID to update
nameNoNew product name
codeNoNew product code
descriptionNoNew product description
unitNoNew unit of measurement
taxNoNew tax percentage
categoryNoNew product category ID
owner_idNoNew owner user ID
is_linkableNoWhether the product can be linked to deals
visible_toNoNew visibility: 1=Owner, 3=Group, 5=Subgroups, 7=Company
pricesNoArray of price objects per currency
custom_fieldsNoCustom field values as object with field keys
billing_frequencyNoBilling frequency
billing_frequency_cyclesNoNumber of billing cycles (max 208, null = unlimited)
Behavior3/5

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

Annotations already declare readOnlyHint false, destructiveHint false, idempotentHint true, openWorldHint true. The description adds that the product must be existing, which is a behavioral prerequisite not in annotations. However, it does not disclose other behaviors like what happens on failure or whether partial updates are supported.

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 a single, concise sentence that front-loads the purpose with no redundancy or wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 14 parameters, nested objects, and no output schema, the description lacks essential context such as typical usage, return value, error handling, or parameter relationships. It is insufficient for an agent to use the tool confidently without additional schema inspection.

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 parameters have descriptions. The tool description does not add any further semantics beyond what the schema provides. Baseline of 3 is appropriate.

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 the verb 'Update' and resource 'existing product', which is specific. However, it does not explicitly differentiate from sibling tools beyond the inherent resource specificity, but the name already indicates it's for products. It is not a tautology because 'existing' adds a nuance.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives like 'create_product' or when not to use it. The description implies the product must exist (says 'existing'), but no explicit prerequisites or context are provided.

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/ckalima/pipedrive-mcp-server'

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