Skip to main content
Glama

files_delete

Permanently delete a file and its associations from Pipedrive. This action cannot be undone, so verify the file first.

Instructions

Delete a file from Pipedrive.

Permanently removes a file and its associations with entities.

Workflow tips:

  • Deleting a file removes it from all associated entities

  • This action cannot be undone

  • Consider using files_get first to verify the file

  • Deleted files may still appear in lists if include_deleted_files=true

Common use cases:

  • Remove file: { "id": 123 }

  • Clean up old attachments

  • Remove duplicate files

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the file to delete
Behavior5/5

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

With no annotations, the description fully discloses permanent deletion, removal from associated entities, irreversibility, and visibility in lists with include_deleted_files=true. Exceeds basic schema info.

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?

Concise, with a clear main sentence, workflow tips, and common use cases. All content is relevant and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple one-parameter tool with no output schema, the description covers behavior, side effects, and use cases completely.

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% for the single 'id' parameter. The description adds an example ('id: 123') but does not provide additional semantics 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 'Delete a file from Pipedrive' and explains permanence and removal of associations, distinguishing it from sibling tools like files_get, files_list, 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 such as verifying with files_get first and warns that deletion cannot be undone. Includes common use cases but does not explicitly state when not to use this tool.

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