Skip to main content
Glama

deals_list_files

Retrieve all files attached to a deal, including names, sizes, upload dates, and download URLs. Supports pagination and sorting.

Instructions

List all files attached to a deal.

Returns all files associated with this deal.

Workflow tips:

  • Shows file names, sizes, and upload dates

  • Includes download URLs for each file

  • Paginated for deals with many files

  • Cached for 5 minutes

Common use cases:

  • List all files: { "id": 123 }

  • Paginated list: { "id": 123, "start": 0, "limit": 50 }

  • Sorted by date: { "id": 123, "sort": "add_time" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the deal
startNoPagination start
limitNoNumber of items to return
sortNoField to sort by (e.g., add_time, file_name)
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses caching behavior (5-minute cache), pagination support, and that download URLs are included. It also mentions the returned fields (file names, sizes, upload dates). It does not cover rate limits, authentication, or link expiration, but for a read-only list tool this is adequate.

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?

The description is well-structured with a summary, workflow tips (bullet points), and common use cases (also bullet points). It is concise and front-loaded with the main purpose. Each section serves a clear function without unnecessary verbosity.

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 there is no output schema, the description adequately covers the return values (file details, download URLs) and behavioral aspects (pagination, caching). It explains the main use cases and parameters. Minor gaps like authentication requirements or pagination limits do not significantly detract from completeness for this simple list tool.

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%, so baseline is 3. The description adds value by providing example values for the id, start, limit, and sort parameters, including a concrete sort example ('add_time'). It also explains the caching and pagination context beyond what the schema provides. This exceeds the baseline.

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 specifies the verb 'list' and resource 'files attached to a deal'. It distinguishes itself from sibling tools like files_list and other deals_list_* tools by explicitly stating it lists files for a specific deal. The description also details what is returned (file names, sizes, upload dates, download URLs).

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 provides common use cases and example invocations for listing all files, paginated lists, and sorted lists. However, it does not explicitly state when to avoid this tool or mention alternative tools like files_list. The workflow tips imply typical usage but lack explicit exclusions.

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