Skip to main content
Glama
Files-com

Files.com MCP Server

Official
by Files-com

List Action Log

List_Action_Log
Read-only

Retrieve and filter action logs from your Files.com account by folder, path, user, or date range.

Instructions

List Action Logs

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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: 2000, 1,000 or less is recommended).
filterNoIf set, return records where the specified field is equal to the supplied value. Valid fields are `folder`, `path`, `src`, `destination`, `created_at`, `user_id` or `username`.
filter_gtNoIf set, return records where the specified field is greater than the supplied value. Valid fields are `created_at`.
filter_gteqNoIf set, return records where the specified field is greater than or equal the supplied value. Valid fields are `created_at`.
filter_prefixNoIf set, return records where the specified field is prefixed by the supplied value. Valid fields are `folder`, `path`, `src`, `destination` or `username`.
filter_ltNoIf set, return records where the specified field is less than the supplied value. Valid fields are `created_at`.
filter_lteqNoIf set, return records where the specified field is less than or equal the supplied value. Valid fields are `created_at`.
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
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the description does not need to reiterate safety. However, the description adds no behavioral context beyond what annotations provide, missing details about pagination, filtering, or return format. This is acceptable given the annotations cover the safety profile.

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

Conciseness2/5

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

The description is extremely concise (3 words) but at the cost of under-specification. It does not earn its place because it adds no meaningful information beyond the name.

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 9 parameters and an output schema, the description fails to explain what action logs are, what fields are returned, or how filtering works. The sibling tools list many specific logs, so context on scope is missing.

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 9 parameters having detailed descriptions. The tool description adds nothing beyond the schema, so a baseline score of 3 is appropriate.

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

Purpose2/5

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

The description 'List Action Logs' is a tautology that restates the tool name without specifying what an action log is or how it differs from sibling tools like List_Api_Request_Log or List_Automation_Log. It provides no unique value.

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 over alternatives, which are numerous and overlapping (e.g., List_Api_Request_Log, List_Ftp_Action_Log).

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