Skip to main content
Glama

persons_list_files

Retrieve all files attached to a person, including metadata and download URLs. Supports pagination and sorting for organized access.

Instructions

List all files attached to a specific person.

Returns all files associated with the person, including:

  • File metadata (name, type, size)

  • Upload information (uploader, timestamps)

  • File URL for download

  • Associated deal/organization if applicable

Supports:

  • Pagination for large file lists

  • Sorting by various fields

This includes files uploaded directly to the person and files from related deals/activities.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesPerson ID
startNoPagination start (default: 0)
limitNoItems per page, max 500 (default: 100)
sortNoField to sort by (e.g., "add_time", "file_name")
Behavior3/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, sorting, and return fields but lacks details on error handling, authentication requirements, or behavior when person does not exist.

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 relatively concise but includes a bullet list and extra details. It could be slightly shorter without losing key information.

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, the description explains return fields well (metadata, upload info, URL, associations). It supports pagination and sorting. Missing error handling info, but complete enough for a listing tool.

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% with all parameters described. The description adds no significant meaning beyond the schema, so baseline 3 is appropriate.

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 lists all files attached to a specific person, with a detailed list of returned information. It distinguishes from sibling tools like deals_list_files by specifying 'person'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for person-specific files and mentions inclusion of related files, but does not explicitly state when to use this tool over alternatives like deals_list_files or organizations_list_files.

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