Skip to main content
Glama
Files-com

Files.com MCP Server

Official
by Files-com

List External Event

List_External_Event
Read-only

Retrieve a list of external events with options to filter by date and status, sort by event type, and paginate results.

Instructions

List External Events

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: 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`, `status` or `event_type`.
filterNoIf set, return records where the specified field is equal to the supplied value. Valid fields are `created_at` and `status`.
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_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 already declare readOnlyHint=true, so the description adds no behavioral context. It does not mention pagination, sorting, filtering, or other behaviors, which are only in the schema. The description contradicts nothing but adds no value beyond annotations.

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 a one-sentence tautology that restates the name. It is under-specified rather than concise; every useful detail is absent.

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, the description omits high-level context such as what constitutes an 'external event' or how this list differs from other list tools. Given the parameter complexity and sibling list tools, the description is insufficient.

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% with detailed descriptions for all 9 parameters. The description adds no extra meaning, but baseline is 3 when schema does the heavy lifting.

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 External Events' uses a specific verb and resource, clearly indicating the tool lists external events. However, it does not differentiate from other list tools (e.g., List_Action_Log) by explaining what 'external' means, leaving ambiguity.

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?

There is no guidance on when to use this tool versus the many sibling list tools (e.g., List_Group, List_User). No context about prerequisites or appropriate scenarios is provided.

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