Skip to main content
Glama
Files-com

Files.com MCP Server

Official
by Files-com

List Ftp Action Log

List_Ftp_Action_Log
Read-only

Retrieve and filter FTP action logs to monitor file transfer activities. Supports filtering by path, user, date range, and more.

Instructions

List FTP 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 `path`, `true_path`, `remote_ip`, `session_uuid`, `success`, `status`, `action_type`, `username` or `created_at`.
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 `path`, `true_path`, `action_type` 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
Behavior2/5

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

Annotations indicate readOnlyHint=true, so the tool is a read operation. The description adds no further behavioral information (e.g., pagination, filtering behavior, or limitations) beyond what annotations and schema already provide.

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 extremely concise (5 words), but it is too minimal and lacks structure. It is efficient but under-informative.

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?

Given the tool has 9 parameters, an output schema, and many siblings, the description is insufficient. It does not explain what FTP action logs are, how they relate to other logs, or any contextual information beyond the bare name.

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 detailed parameter descriptions. The description does not add any extra meaning beyond the schema, so it meets the baseline but does not improve it.

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 clearly states the tool lists FTP action logs, which is a specific resource. However, it does not differentiate from sibling tools like List_Sftp_Action_Log or List_Action_Log, making the purpose slightly less distinct.

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 guidance is provided on when to use this tool versus alternatives. With many similar logging tools as siblings (e.g., List_Sftp_Action_Log, List_Web_Dav_Action_Log), the description fails to clarify use cases.

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