Skip to main content
Glama

list_files

Read-only

List direct files and folders in a folder, up to 200 per page, sorted by name, size, or updated time. Identify by parent_id or absolute path, or omit both for root.

Instructions

List the direct children (files and folders) of one folder, up to 200 per page, sorted by name (default), size or updated_at. Identify the folder by parent_id or absolute path; omit both for the root. Each item has id, kind, size, mime and updated_at; the result also has total and next_cursor, which you pass back as cursor for the next page. Does not recurse: to find items anywhere in the drive use search_files (by name) or search_file_contents (by text inside files). Requires files:read.

Input Schema

NameRequiredDescriptionDefault
descNosort descending
pathNoabsolute folder path instead of parent_id
orderNosort order: name, size, or updated_at
cursorNocursor returned by the previous call
parent_idNofolder node ID; omit for root

Output Schema

NameRequiredDescriptionDefault
itemsYes
totalYes
next_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Goes well beyond the readOnlyHint annotation by disclosing the 200-item page cap, the default sort order, the non-recursive behavior, the requirement for files:read, and how next_cursor feeds back into cursor. It does not cover error behavior for a bad parent_id/path, which keeps it from the top score given annotations already carry the safety profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the core action, then addressing identifiers, response shape/paging, and the sibling boundary. Every clause carries operative information for a caller.

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

Completeness5/5

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

For a paginated list tool with a full output schema and annotations, the definition covers scope, paging, sorting, identifier options, and permissions without redundancy. Nothing an agent needs to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds real meaning: 'name' is the default order, parent_id and path are mutually exclusive substitutes, and cursor should be the previous call's next_cursor. The desc parameter's interaction with order is left implicit.

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

Purpose5/5

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

States a specific verb and resource ('List the direct children ... of one folder') with scope ('does not recurse') and paging limits. It names the sibling tools that cover the non-recursive case (search_files, search_file_contents), so an agent can distinguish it from them without opening the schema.

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

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit routing guidance: omit parent_id and path for root, use path instead of parent_id as an alternative, and use search_files or search_file_contents when recursion or cross-drive lookup is needed. This covers when-to-use, when-not-to-use and the alternatives in a single sentence.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.