Skip to main content
Glama

list_folder

List documents and subfolders inside a Laserfiche folder by its ID for browse-style navigation.

Instructions

List the immediate children (documents and subfolders) of a folder by ID.

Use this for browse-style navigation when the user references a known folder. The root folder is typically ID 1 — start there if you have nothing else. To navigate from a path string, resolve it first with get_entry_by_path. To search across the whole repo, use search_natural or search_entries.

Args: folder_id: Integer entry ID of the parent folder. max_results: Page size (default 25, capped by LF_MAX_RESULTS_CEILING). skip: 0-indexed offset for pagination. Combine with max_results to walk a large folder in chunks; check next_link to know when to stop.

Returns: SearchResults with entries, total_count (server fills it only when the build supports $count), and next_link. Each entry has id, name, entry_type, full_path, creation_time, and last_modified_time. Drill into a single entry with get_entry or get_field_values.

On failure: returns {"mode": "error", "error": <slug>, "folder_id": <int>, ...}. Common slugs: not_found (folder ID doesn't exist), auth_failed (no read permission).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
folder_idYesInteger entry ID of the parent folder. The root folder is typically ID 1.
max_resultsNoPage size (default 25, capped by LF_MAX_RESULTS_CEILING).
skipNo0-indexed offset for pagination. Combine with max_results to walk a large folder in chunks; check next_link to know when to stop.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

Details pagination behavior, max_results cap, return format including conditional total_count, and error slugs like not_found and auth_failed, with no annotations to contradict.

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?

Well-structured with purpose first, then usage, parameters, returns, and errors; all sentences are informative and focused.

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?

Given moderate complexity, the description covers all aspects: purpose, usage, parameters, return format with fields, pagination, and error handling, making it self-contained.

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?

Input schema has 100% coverage, and description adds context like root folder default, page size default, and pagination usage, slightly exceeding baseline.

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?

The description clearly states it lists immediate children of a folder by ID, using specific verbs and resources, and distinguishes it from siblings like search_natural and get_entry_by_path.

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 states when to use (browse-style navigation for known folders), provides default root ID, and names alternatives for path resolution and global search.

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/SamuelSHernandez/laserfiche-mcp'

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