Skip to main content
Glama
Files-com

Files.com MCP Server

Official
by Files-com

List Automation Log

List_Automation_Log
Read-only

Retrieve automation logs with filters for automation ID, run ID, operation, path, status, or creation date. Supports pagination.

Instructions

List Automation 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 `automation_id`, `automation_run_id`, `operation`, `path`, `status` 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`.
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?

The description adds no behavioral context beyond the readOnlyHint annotation. It does not disclose any potential side effects, return format details, or other behavioral traits that would help the agent understand the tool's behavior.

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 brief (two words), which is concise but not effective. It does not front-load any useful information beyond what the name provides, and the brevity fails to convey purpose or usage.

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 having an output schema (implied by the 'fields' parameter description), the description does not explain the return values, pagination behavior, or typical use cases. For a tool with many siblings, this incompleteness hinders correct selection.

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 in the schema. The description adds no additional meaning to parameters, so baseline score of 3 is appropriate given high schema coverage.

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?

Description 'List Automation Logs' is a tautology of the tool name and does not specify what an automation log is or how it differs from other list tools like List_Automation or List_Action_Log. It lacks a specific verb and resource context beyond the name itself.

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 the many sibling list tools. There is no mention of prerequisites, alternatives, or specific scenarios where listing automation logs is appropriate.

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