Skip to main content
Glama
Files-com

Files.com MCP Server

Official
by Files-com

List Settings Change

List_Settings_Change
Read-only

Retrieve a paginated list of settings changes, filterable by API key or user ID, and sortable by date or user.

Instructions

List Settings Changes

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`, `api_key_id` or `user_id`.
filterNoIf set, return records where the specified field is equal to the supplied value. Valid fields are `api_key_id` and `user_id`.
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
Behavior1/5

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

Annotations declare readOnlyHint=true, but the description adds no behavioral context beyond that. It does not mention pagination, filtering, or any other behavioral traits.

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 short but it is under-specification, not conciseness. It fails to convey any useful information that earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 5 parameters and an output schema, the description is completely inadequate. It does not explain the return value, filter options, or sorting capabilities.

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 per guidelines the baseline is 3. The description adds no additional meaning to parameters, but the schema itself is comprehensive.

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

Purpose1/5

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

The description 'List Settings Changes' is a tautology, merely restating the tool name. It fails to specify what constitutes a settings change or what the tool actually lists.

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 alternative list tools such as List_History or List_Action_Log. The description offers no context for selection.

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