Skip to main content
Glama
Files-com

Files.com MCP Server

Official
by Files-com

List For User History

List_For_User_History
Read-only

Retrieve activity history for a specific user with optional date filters and pagination.

Instructions

List history for specific user.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
start_atNoLeave blank or set to a date/time to filter earlier entries.
end_atNoLeave blank or set to a date/time to filter later entries.
displayNoDisplay format. Leave blank or set to `full` or `parent`.
cursorNoUsed for pagination. When a list request has more records available, cursors are provided in the response headers `X-Files-Cursor-Next` and `X-Files-Cursor-Prev`. Send one of those cursor value here to resume an existing list from the next available record. Note: many of our SDKs have iterator methods that will automatically handle cursor-based pagination.
per_pageNoNumber of records to show per page. (Max: 10000, 1,000 or less is recommended).
sort_byNoIf set, sort records by the specified field in either `asc` or `desc` direction. Valid fields are `created_at`.
user_idNoUser ID.
fieldsNoOptional list of attribute names to include as columns in the response table. When omitted, a sensible default set is used. Useful for narrowing wide entities or surfacing fields not in the default.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

Annotations declare readOnlyHint=true, so the description doesn't need to state that. However, it adds no behavioral details beyond the one-line description. It doesn't explain pagination, filtering, or data scope, which are important for a list tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise. However, it is too minimal and does not fully earn its place given the tool's complexity (8 parameters) and the need to distinguish from many sibling tools.

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

Completeness2/5

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

Despite an output schema existing, the description fails to explain what 'history' entails or how to effectively use the parameters. It is insufficient for a tool with 8 optional parameters and many sibling tools, leaving the agent without crucial context.

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 description coverage is 100%, so parameters are well-documented in the schema. The description adds no extra meaning or usage hints for parameters, meeting the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List history for specific user' clearly states the verb 'list' and the resource 'history for specific user'. It distinguishes from siblings like 'List_History' and 'List_For_File_History' by specifying user-focused history, but lacks further differentiation details.

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

Usage Guidelines2/5

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

No usage guidance is provided. The description does not indicate when to use this tool versus alternatives such as 'List_Logins_History' or 'List_History', nor does it mention prerequisites or contexts.

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/Files-com/files-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server