Skip to main content
Glama
comma-compliance

pipedrive-mcp

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

pipedrive_deal_products_add

Attach a product to a deal by specifying price per unit and quantity. Use it to add line items to Pipedrive deals with optional discounts or product variations.

Instructions

Attach a product to a deal with price/quantity.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deal_idYesThe deal ID
commentsNo
discountNo
quantityYesQuantity
item_priceYesPrice per unit
product_idYesThe product ID to attach
tax_methodNo
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.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It implies a mutation ('attach') but never states permission requirements, what happens when a product is already attached, whether the call is idempotent, or what the response contains. For a write 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.

Conciseness4/5

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

A single tight sentence with the core action front-loaded and no filler. It is efficient, though arguably too terse given the tool's 8-parameter complexity.

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?

For a mutation tool with 8 parameters, no annotations, and no output schema, the description is far too thin. It leaves undocumented parameters, side effects, and error/return behavior entirely unaddressed.

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 coverage is only 63%, and the description adds nothing beyond echoing 'price/quantity'. Optional parameters like discount, tax_method, comments, and product_variation_id are left entirely to the (partially undocumented) schema, so the description fails to compensate for the coverage gap.

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+resource ('Attach a product to a deal') and hints at the key fields (price/quantity), so an agent immediately knows the operation. It does not, however, distinguish itself from the sibling pipedrive_deal_products_update or explain the relationship to product_variations.

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?

There is no guidance on when to use this versus pipedrive_deal_products_update or pipedrive_deal_products_list, nor any stated prerequisites (e.g., the deal and product must already exist). The agent must infer all usage 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