Skip to main content
Glama
comma-compliance

pipedrive-mcp

by comma-compliance
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Remote

pipedrive_deal_products_update

Update a product attached to a deal by changing its quantity, price, discount, tax method, comments, or variation. Use deal ID and deal-product ID to apply the changes.

Instructions

Update a product attachment on a deal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deal_idYesThe deal ID
commentsNo
discountNo
quantityNo
item_priceNo
tax_methodNo
deal_product_idYesThe deal-product attachment ID
product_variation_idNoOptional product variation ID (from pipedrive_product_variations_list)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.1
    • addedInput schema / properties / product_variation_id
      Added value: +{
+  "description": "Optional product variation ID (from pipedrive_product_variations_list)",
+  "minimum": 0,
+  "type": "integer"
+}
  2. First observedv1.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden. 'Update' implies mutation, but nothing is said about partial vs. full update semantics, whether omitted fields are cleared, required permissions, or reversibility. For a mutation tool with zero annotation coverage, this is a significant gap.

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

Conciseness3/5

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

A single front-loaded sentence with no wasted words, but for an 8-parameter mutation it is under-specified rather than genuinely concise. Brevity here comes at the cost of usefulness.

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 8 parameters, low schema coverage, no annotations, and no output schema, the description is far too thin. An agent gets no field semantics, no update behavior, and no return expectations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 38% — 6 of 8 parameters (comments, discount, quantity, item_price, tax_method, product_variation_id) lack schema descriptions. The description names no parameters at all, so it fails to compensate for the coverage shortfall on this 8-param tool.

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?

States a specific verb (Update) and resource (product attachment on a deal), which is distinguishable from siblings like pipedrive_deal_products_add, _delete, and _list. It's clear but does not explicitly name or contrast against those siblings.

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 versus pipedrive_deal_products_add, _delete, or pipedrive_deals_update. No prerequisites (e.g., the deal product must already exist) are stated, leaving the agent to infer context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools