Skip to main content
Glama

files_list

Retrieve paginated lists of files filtered by associated entities like deals, persons, or organizations, with sorting and pagination options.

Instructions

List files with pagination and filtering options.

Returns a paginated list of files. Use filters to narrow results by associated entity (deal, person, organization, activity, product).

Workflow tips:

  • Filter by entity to get files for specific deals, persons, organizations, etc.

  • Use sort to order by add_time, update_time, file_name, or file_size

  • Set include_deleted_files=true to see deleted files

  • Use start/limit for pagination (default limit: 100, max: 500)

  • Combine multiple filters to narrow results

Common use cases:

  • List all files for a deal: { "deal_id": 123 }

  • List all files for a person: { "person_id": 456 }

  • List all files for an organization: { "org_id": 789 }

  • List recent files sorted by upload time: { "sort": "add_time", "sort_by": "desc" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deal_idNoFilter by deal ID
person_idNoFilter by person ID
org_idNoFilter by organization ID
activity_idNoFilter by activity ID
product_idNoFilter by product ID
include_deleted_filesNoWhether to include deleted files (default: false)
sortNoField to sort by (e.g., add_time, update_time, file_name, file_size)
sort_byNoSort direction
startNoPagination start
limitNoNumber of items to return
Behavior4/5

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

With no annotations, the description carries full burden. It discloses pagination behavior (default limit 100, max 500), sorting options, and the include_deleted_files flag. It omits details like default sort order or response structure, but covers key behaviors sufficiently.

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 concise, starting with a one-sentence summary followed by bullet points and examples. Every sentence adds utility; no redundancy or fluff.

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 10 parameters and no output schema, the description covers pagination, filtering, sorting, and common use cases adequately. It lacks information on error handling or default sorting order, but for a list tool, completeness is high.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds significant value by listing sortable fields (add_time, update_time, file_name, file_size) and providing concrete examples of parameter combinations (e.g., '{ "deal_id": 123 }'). This goes well beyond the schema's property descriptions.

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 'List files with pagination and filtering options', specifying the verb and resource. The examples (e.g., 'List all files for a deal') distinguish it from entity-specific list tools like deals_list_files, making its purpose unambiguous.

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, e.g., filtering by entity and using pagination. However, it does not explicitly exclude alternatives like deals_list_files when listing files for a specific entity, so guidance on when to use this vs. sibling tools is incomplete.

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