Skip to main content
Glama

files_update

Update the name or description of a file in Pipedrive without modifying its content.

Instructions

Update file metadata (name or description).

Updates a file's name or description. Does not modify the actual file content.

Workflow tips:

  • Can update file name (without extension) or description

  • Name must not exceed 255 characters

  • Description limited to 1000 characters

  • At least one field (name or description) should be provided

Common use cases:

  • Rename file: { "id": 123, "name": "Updated Contract" }

  • Add description: { "id": 123, "description": "Q4 2024 sales contract" }

  • Update both: { "id": 123, "name": "Contract V2", "description": "Updated terms" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the file to update
nameNoNew name for the file (max 255 chars)
descriptionNoDescription of the file (max 1000 chars)
Behavior5/5

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

No annotations provided, so description carries full burden. It explicitly states no content modification, character limits, and that at least one field is required. Fully transparent about tool's behavior.

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 short summary, workflow tips, and examples. Every sentence adds value. Front-loaded with core action and constraints.

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 what the tool does and constraints. Lacks mention of return value (e.g., updated file object or success status), but given simplicity, it 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 has 100% coverage, so baseline is 3. Description adds value with examples, character limits, and reminder that name should be without extension. Exceeds minimal requirements.

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 it updates file metadata (name or description) and explicitly notes it does not modify content. It distinguishes itself from sibling tools like files_upload or files_delete by specifying its scope.

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 clear guidance on when to use (rename, update description) with workflow tips and common use cases. Does not explicitly state when not to use, but the context is sufficiently 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