Skip to main content
Glama

files_upload

Upload a file from your local path and attach it to any Pipedrive entity including deals, contacts, or organizations.

Instructions

Upload a file to Pipedrive and attach it to a deal, person, organization, activity, or product.

Uploads a file from the specified file path and associates it with at least one entity.

Workflow tips:

  • Provide the full file path to upload

  • At least one entity ID must be provided (deal_id, person_id, org_id, activity_id, or product_id)

  • The file name will be extracted from the path automatically

  • Supports all common file types (documents, images, videos, etc.)

  • Maximum file size depends on your Pipedrive plan

Common use cases:

  • Attach contract to deal: { "file_path": "/path/contract.pdf", "deal_id": 123 }

  • Add profile photo to person: { "file_path": "/path/photo.jpg", "person_id": 456 }

  • Upload document to organization: { "file_path": "/path/doc.docx", "org_id": 789 }

  • Attach multiple entities: { "file_path": "/path/file.pdf", "deal_id": 123, "person_id": 456 }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYesPath to the file to upload
deal_idNoID of the deal to attach the file to
person_idNoID of the person to attach the file to
org_idNoID of the organization to attach the file to
activity_idNoID of the activity to attach the file to
product_idNoID of the product to attach the file to
lead_idNoID of the lead to attach the file to
Behavior3/5

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

No annotations provided, so description must carry full burden. Mentions file name extraction and max file size dependency, but lacks details on side effects (e.g., overwrite behavior), error handling, or authentication. Adequate but not comprehensive.

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?

Well-structured with workflow tips and use cases. First sentence conveys purpose efficiently. Slightly lengthy but every sentence adds value; no redundancy.

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?

Covers purpose, required parameters, entity associations, file types, and size limits. Lacks output/response specification, but for an upload tool the return value is less critical. Adequate for agent decision-making.

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%, but description adds value by explaining that at least one entity ID (deal_id, person_id, etc.) must be provided, which is not enforced by the schema. Provides examples mapping parameters to use cases.

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 'Upload a file to Pipedrive and attach it to a deal, person, organization, activity, or product.' It specifies the resource (file) and action (upload and attach) and distinguishes it from sibling file tools (e.g., download, delete) by focusing on upload.

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 workflow tips (full path, at least one entity ID, file name extraction, supported types, max size) and common use cases with JSON examples. Does not explicitly state when not to use, but the context makes it clear for upload scenarios.

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