Skip to main content
Glama
ckalima

Pipedrive MCP Server

pipedrive_upload_product_image

Upload a product image to Pipedrive using file path or base64 data. Supports PNG, JPEG, GIF, and WebP formats.

Instructions

Upload an image for a product. Provide the image via EITHER file_path OR base64_data (exactly one required). Supports png, jpeg, gif, and webp. Note: file_path is read by the SERVER process via the filesystem and is disabled by default; the operator must set PIPEDRIVE_IMAGE_BASE_DIR and the path must resolve within it; otherwise use base64_data, which is transport-safe.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe product ID
file_pathNoPath the server reads via fs.readFile, confined to PIPEDRIVE_IMAGE_BASE_DIR (filesystem reads are disabled unless that variable is set). Mutually exclusive with base64_data.
base64_dataNoBase64-encoded image bytes (transport-safe). Mutually exclusive with file_path.
file_nameYesOriginal filename including extension (e.g. product.png)
mime_typeNoMIME type. Inferred from file_name if omitted.
Behavior5/5

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

Annotations are minimal, but the description adds critical details: file_path is read server-side, disabled by default, requires PIPEDRIVE_IMAGE_BASE_DIR. Also notes supported formats. No contradictions.

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?

Two concise sentences that front-load the purpose and key constraint, with no wasted words. Every sentence earns its place.

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?

No output schema, so description should ideally mention return values (e.g., image URL). Missing details on response format, size limits, or error handling. Otherwise adequate for a 5-param tool.

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 baseline is 3. Description reinforces mutual exclusivity and adds server-side context for file_path, adding value beyond the schema.

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?

Clearly states 'Upload an image for a product' with a specific verb and resource. Differentiates from siblings like get_product_image and update_product_image 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 Guidelines4/5

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

Provides explicit guidance on when to use file_path vs base64_data, including the server configuration prerequisite. Does not explicitly mention when not to use compared to update, but the context is clear.

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/ckalima/pipedrive-mcp-server'

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