Skip to main content
Glama

deals_update_product

Update product details attached to a deal, such as price, quantity, discount, or comments. Specify the deal ID and product attachment ID to modify parameters without changing the product.

Instructions

Update a product attached to a deal.

Modifies the price, quantity, discount, or other details of a product already attached to a deal.

Workflow tips:

  • Use deals/list_products to get product_attachment_id

  • product_attachment_id is NOT the same as product_id

  • Only specify fields you want to update

  • Cannot change the actual product, only its parameters

Common use cases:

  • Update quantity: { "id": 123, "product_attachment_id": 789, "quantity": 5 }

  • Change price: { "id": 123, "product_attachment_id": 789, "item_price": 149.99 }

  • Add discount: { "id": 123, "product_attachment_id": 789, "discount_percentage": 20 }

  • Update multiple: { "id": 123, "product_attachment_id": 789, "quantity": 3, "discount_percentage": 10, "comments": "Updated terms" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the deal
product_attachment_idYesID of the deal-product attachment to update
item_priceNoUpdated price
quantityNoUpdated quantity
discount_percentageNoUpdated discount percentage (0-100)
durationNoUpdated duration
commentsNoUpdated comments
enabled_flagNoWhether the product is enabled
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses that it modifies parameters and clarifies 'Cannot change the actual product, only its parameters'. Missing auth needs, idempotency, or error conditions, but adds useful constraint info.

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?

Well-structured with summary, workflow tips, and common use cases. Each sentence adds value; no wasted words. Front-loaded with key purpose.

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?

Given 8 parameters, 2 required, and no output schema, description provides sufficient examples and workflow guidance. Missing details on return format or error handling, but overall complete for an agent to use correctly.

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 has 100% coverage with descriptions, but description adds value beyond schema: examples show typical values, workflow tips clarify parameter semantics (e.g., product_attachment_id vs product_id), and that only specified fields are updated.

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 a product attached to a deal', uses a specific verb (Update) and resource, and differentiates from sibling tools like deals_add_product and deals_remove_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?

Provides explicit workflow tips (use deals/list_products for attachment ID, distinguish product_attachment_id from product_id) and common use cases with examples. No explicit when-not, but clear when to use.

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