Skip to main content
Glama

products_create

Add a new product to your Pipedrive CRM by providing a name and optional details like SKU, prices, and custom fields.

Instructions

Create a new product in Pipedrive.

Required fields:

  • name: Product name

Optional fields:

  • code: Product code (SKU)

  • description: Product description

  • unit: Unit type (e.g., "pcs", "kg", "hours")

  • tax: Tax percentage (0-100)

  • active_flag: Whether product is active (default: true)

  • selectable: Whether product can be selected in deals (default: true)

  • visible_to: Visibility level (1=owner only, 3=entire company)

  • owner_id: User who will own this product

  • prices: Array of price objects with format: [{"price": 100, "currency": "USD", "cost": 50}]

  • billing_frequency: One of: one-time, weekly, monthly, quarterly, semi-annually, annually

  • billing_frequency_cycles: Number of billing cycles

Custom fields:

  • Pass display names: { "custom_fields": { "SKU Class": "A", "Category": "Electronics" } }

  • Or hash keys directly: { "custom_fields": { "abc123...": "raw value" } }

  • For enum/set fields, pass option labels (not ids).

Example prices array: { "prices": [ {"price": 100, "currency": "USD", "cost": 50, "overhead_cost": 10, "notes": "Standard price"}, {"price": 85, "currency": "EUR", "cost": 45} ] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taxNoTax percentage (0-100)
codeNoProduct code/SKU
nameYesProduct name (required)
unitNoUnit type (e.g., pcs, kg, hours)
pricesNoArray of price objects
owner_idNoID of the user who will own this product
selectableNoWhether product can be selected in deals
visible_toNoVisibility: 1 (owner only), 3 (entire company)
active_flagNoWhether product is active
descriptionNoProduct description
custom_fieldsNoCustom field values keyed by display name or hash.
billing_frequencyNoBilling frequency
billing_frequency_cyclesNoNumber of billing cycles
Behavior3/5

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

With no annotations provided, the description carries full burden. It explains how to pass custom fields and provides an example for prices, but does not disclose side effects (e.g., what happens on creation), permission requirements, rate limits, or response format. This is adequate but incomplete.

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 sections (intro, required, optional, custom fields, example). It is somewhat verbose but each sentence adds value. No wasted words, though could be slightly more concise.

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?

For a tool with 13 parameters and no output schema, the description covers all parameters with examples and detailed custom field handling. Missing return value description (e.g., created product object) and behavioral constraints, but overall fairly complete.

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

Parameters5/5

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

Schema coverage is 100%, baseline 3. The description significantly adds meaning: explains two methods for custom fields, lists enum values for billing_frequency, provides complete prices array example, and describes each parameter's purpose. This exceeds baseline.

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 'Create a new product in Pipedrive.' This is a specific verb+resource combination that distinguishes it from sibling create tools like deals_create or persons_create.

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

Usage Guidelines3/5

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

The description lists required and optional fields but does not explicitly state when to use this tool versus alternatives. It lacks guidance on prerequisites, use cases, or exclusions, relying on implied usage from the entity type.

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/nubiia-dev/mcp-pipedrive'

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