Skip to main content
Glama

laserfiche_folder_list

Lists documents and subfolders in a Laserfiche folder by ID for browse navigation. Supports pagination with max_results and skip parameters.

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?

With no annotations provided, the description fully covers behavioral traits: pagination details (max_results, skip, next_link), total_count availability, return structure, and error slugs (not_found, auth_failed). This is comprehensive for a listing tool.

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?

The description is well-organized with Args and Returns sections, but it is slightly verbose for a simple tool. It could be trimmed while retaining all information, but it is not overly long and is front-loaded with purpose.

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 the presence of an output schema, the description goes beyond expectations by detailing pagination, error handling, entry fields, and suggesting next steps (get_entry, get_field_values). It is fully complete for the tool's complexity.

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 coverage is 100%, so the baseline is 3. The description adds value by providing practical usage context (e.g., 'root is typically ID 1', 'check next_link to know when to stop'), which enhances understanding beyond the schema descriptions alone.

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 states 'List the immediate children (documents and subfolders) of a folder by ID,' which is a specific verb and resource. It distinguishes itself from siblings like get_entry_by_path (path resolution) and search_natural/search_entries (full repository search) by explicitly mentioning alternatives.

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?

The description clearly states when to use ('browse-style navigation when the user references a known folder') and when not to use ('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').

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