Skip to main content
Glama

files_create_remote_link

Create a link to a file stored in Google Drive, Dropbox, OneDrive, Box, or SharePoint and associate it with a Pipedrive entity like a deal or person.

Instructions

Link a remote file from Google Drive, Dropbox, OneDrive, Box, or SharePoint.

Creates a link to a file stored in external cloud storage and associates it with a Pipedrive entity.

Workflow tips:

  • Supported platforms: googledrive, dropbox, onedrive, box, sharepoint

  • Provide the remote file's ID from the cloud storage platform

  • Specify which entity type and ID to link to

  • Remote files appear alongside uploaded files in Pipedrive

Common use cases:

  • Link Google Drive file to deal: { "item_type": "deal", "item_id": 123, "remote_id": "1a2b3c", "remote_location": "googledrive" }

  • Link Dropbox file to person: { "item_type": "person", "item_id": 456, "remote_id": "xyz789", "remote_location": "dropbox" }

  • Link OneDrive file to org: { "item_type": "organization", "item_id": 789, "remote_id": "abc123", "remote_location": "onedrive" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
item_typeYesType of item to link the file to
item_idYesID of the item to link the file to
remote_idYesID of the file in the remote system
remote_locationYesRemote file storage location
Behavior3/5

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

No annotations provided. The description explains the tool creates a link and associates it with an entity, but does not detail permissions, side effects, or error conditions. Adequate but not exhaustive.

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?

The description is well-organized with sections for workflow tips and common use cases. It is concise yet informative, with no unnecessary repetition.

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?

Given no output schema or annotations, the description covers purpose, parameters, workflow, and examples. It lacks details on error handling or authentication, but is mostly complete.

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% with descriptions. The tool description adds extra value by providing examples and explaining how parameters map to use cases, going 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?

The description clearly states the tool creates a link from remote cloud storage to a Pipedrive entity, listing supported platforms and providing detailed examples. It distinguishes from siblings like 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?

The description includes workflow tips, supported platforms, required parameters, and common use cases. It does not explicitly mention when not to use or alternatives, but 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/iamsamuelfraga/mcp-pipedrive'

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