Skip to main content
Glama

list_files

Browse file metadata with filters by project, tag, favorite, folder, or untagged, and paginate results to estimate token counts before reading file contents.

Instructions

List file metadata with optional filters (project_id, tag, favorite, folder, untagged) and pagination. Read-only; no side effects, auth, or rate limits. Each row is annotated with tags, est_tokens, and size_bytes; the response includes total_est_tokens so you can budget before reading bodies. project_id: null returns ONLY Knowledge Base files; omit the field to span everything. Use to browse known structure; for keyword/content lookup use search; for a denser whole-vault dump use project_map.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNoFilter by project ID. Pass null to list ONLY Knowledge Base files (project_id IS NULL).
tagNoFilter by tag name
favoriteNoFilter by favorite status
folderNoFilter by folder path
untaggedNoIf true, return only files that have no tags. Useful for bulk-tagging workflows.
limitNoMaximum number of results
offsetNoOffset for pagination
Behavior4/5

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

States read-only, no side effects, auth, or rate limits; mentions response includes total_est_tokens for budgeting. Could note potential performance but sufficient.

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

Conciseness4/5

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

Well-structured, each sentence adds value, but slightly verbose. Could be tightened slightly.

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?

Covers all aspects: filters, pagination, side effects, response fields, special values, usage guidance. Complete given no output schema or annotations.

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?

Adds meaning beyond 100% coverage schema: explains null project_id for Knowledge Base, untagged for bulk-tagging, and response field total_est_tokens.

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?

Description clearly states the verb 'list' and resource 'files', specifies optional filters and pagination, and distinguishes from siblings 'search' and 'project_map'.

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?

Explicitly tells when to use this tool vs alternatives (search for keyword/content, project_map for dense dump) and clarifies special meaning of project_id=null.

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/safiyu/ctxnest'

If you have feedback or need assistance with the MCP directory API, please join our Discord server