Skip to main content
Glama
Files-com

Files.com MCP Server

Official
by Files-com

List Email Log

List_Email_Log
Read-only

Retrieve a paginated list of email logs with filters by status and creation date. Manage audit trails and monitor email delivery history.

Instructions

List Email 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 `status` and `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_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 agent knows it is a safe read operation. The description adds no further behavioral context (e.g., no mention of rate limits, data freshness, or filtering behavior beyond what the schema provides). Improvement is possible but annotations carry the burden.

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 (3 words), but it sacrifices informativeness. While front-loaded, it lacks content to be considered well-structured.

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?

With 8 optional parameters, a rich output schema, and many sibling tools, the description is too minimal. It omits context about typical use cases, return data shape, or how to effectively use filtering/pagination.

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 the input schema fully documents all 8 parameters. The description adds no additional meaning beyond the parameter names.

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

Purpose3/5

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

The description 'List Email Logs' clearly states the verb and resource, but it does not differentiate this tool from many sibling list tools (e.g., List_Action_Log, List_Api_Request_Log). Without additional context, an agent may confuse which log this retrieves.

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

Usage Guidelines1/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. Given a long list of sibling tools with similar names, an explicit usage recommendation is essential.

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