Skip to main content
Glama

deals_attach_file

Attach a file to a Pipedrive deal using its local path. Supports PDF, DOC, images; file becomes part of the deal's audit trail.

Instructions

Attach a file to a deal.

Uploads and attaches a file to the deal. Useful for contracts, proposals, presentations, etc.

Workflow tips:

  • Provide absolute file path on the local system

  • File will be uploaded to Pipedrive

  • Supports common formats: PDF, DOC, XLS, images, etc.

  • File becomes part of the deal's audit trail

Common use cases:

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

  • Attach proposal: { "id": 456, "file_path": "/path/to/proposal.docx" }

  • Attach image: { "id": 789, "file_path": "/path/to/diagram.png" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the deal
file_pathYesAbsolute path to the file to attach
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 the file is uploaded to Pipedrive and becomes part of the audit trail, but lacks details on error handling, overwrite behavior, or permissions. 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with clear sections (main action, workflow tips, use cases) and bullet points. Every sentence adds value, no redundancy, and key information is front-loaded.

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?

No output schema and description omits return value (e.g., success status, file ID). For a mutation tool, knowing the response is important for agent decision-making after invocation.

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

Parameters3/5

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

Schema coverage is 100% with clear descriptions. The description adds examples and workflow tips (e.g., absolute file path), but these largely reiterate schema info without adding new semantic constraints or format details.

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 ('Attach a file to a deal') and the resource, with specific use cases (contracts, proposals) and examples, making it distinct from sibling tools like deals_create or files_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 and common use cases with example JSON, guiding when to use the tool (e.g., attaching contracts, proposals). However, it does not explicitly differentiate from alternatives like files_upload or mention when not to use it.

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