Skip to main content
Glama

products_create

Create a new product in Pipedrive by specifying name, pricing, billing frequency, and visibility settings.

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

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
nameYesProduct name (required)
codeNoProduct code/SKU
descriptionNoProduct description
unitNoUnit type (e.g., pcs, kg, hours)
taxNoTax percentage (0-100)
active_flagNoWhether product is active
selectableNoWhether product can be selected in deals
visible_toNoVisibility: 1 (owner only), 3 (entire company)
owner_idNoID of the user who will own this product
pricesNoArray of price objects
billing_frequencyNoBilling frequency
billing_frequency_cyclesNoNumber of billing cycles
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It does not mention permissions, side effects, idempotency, rate limits, or what happens on success/failure. It only lists fields, which is insufficient for a mutation tool.

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?

The description is lengthy but well-structured with sections and an example. However, it repeats most schema descriptions verbatim, and could be more concise by omitting redundant details.

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?

While the description thoroughly documents input fields, it lacks information about the return value (no output schema) and error handling. For a creation tool, it should at least indicate that the created product object is returned, which is absent.

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?

The schema provides 100% coverage of parameter descriptions. The description adds value by grouping fields as required/optional, indicating default values (e.g., active_flag defaults to true), and providing an example for the complex prices array, which aids understanding.

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 the action ('Create a new product') and the target resource ('in Pipedrive'), with a list of required and optional fields. It distinguishes itself from sibling tools like products_update or products_delete by focusing on creation.

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 does not explicitly state when to use this tool versus alternatives or mention prerequisites. However, among a large sibling list, the purpose of creation is obvious, and no conflicting sibling tool exists for the same action.

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