Skip to main content
Glama

deals_add_product

Attach a product to a Pipedrive deal, specifying price, quantity, discount, and subscription duration.

Instructions

Add a product to a deal.

Attaches a product to the deal with specific pricing, quantity, and discount.

Workflow tips:

  • Use products/search or products/list to find product IDs

  • Product must exist in Pipedrive catalog

  • Specify item_price to override default product price

  • Quantity defaults to 1 if not specified

  • Discount is percentage (0-100)

  • Duration is for subscription products

Common use cases:

  • Add basic product: { "id": 123, "product_id": 456 }

  • With custom price: { "id": 123, "product_id": 456, "item_price": 99.99, "quantity": 2 }

  • With discount: { "id": 123, "product_id": 456, "quantity": 10, "discount_percentage": 15 }

  • Subscription: { "id": 123, "product_id": 456, "duration": 12, "comments": "Annual subscription" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the deal
product_idYesID of the product to add
item_priceNoPrice at which this product will be added
quantityNoQuantity of items (default: 1)
discount_percentageNoDiscount percentage (0-100, default: 0)
durationNoDuration for subscription products
product_variation_idNoID of the product variation
commentsNoAdditional comments about the product
enabled_flagNoWhether the product is enabled (default: true)
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 discloses that the tool attaches a product with optional pricing, quantity, and discount, and that the product must exist. However, it does not mention error handling, idempotency, or permissions, leaving some behavioral aspects unclear.

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 a clear purpose statement, followed by workflow tips and common use cases. It is front-loaded and each section adds value, though the second sentence ('Attaches a product...') is slightly redundant with the first.

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

Completeness3/5

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

Given 9 parameters and no output schema, the description covers major use cases but omits details on parameters like product_variation_id and enabled_flag. It does not explain the response structure, and while examples are helpful, they do not cover all scenarios, leaving some gaps for an agent.

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%, so the description's added value is moderate. The workflow tips explain parameter usage (e.g., discount_percentage is 0-100, duration for subscriptions) and the common use cases provide example JSON that clarifies how parameters are combined, going beyond the schema descriptions.

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 'Add a product to a deal' and elaborates with specific actions like attaching with pricing, quantity, and discount. It includes common use cases that reinforce the purpose and distinguish it from sibling tools like deals_remove_product or deals_update_product.

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 workflow tips such as using products/search to find product IDs, noting that item_price overrides default, quantity defaults to 1, and discount is a percentage. However, it does not explicitly state when not to use this tool or mention alternative tools like deals_update_product for modifications.

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