Skip to main content
Glama

get_entry

Retrieve full metadata for a Laserfiche entry by its ID: name, type, path, parent, template, page count, and timestamps.

Instructions

Fetch metadata for a single entry by ID.

Use this once you have an entry ID (from search, list_folder, or get_entry_by_path) and need the entry's full metadata: name, type (Folder vs Document), full path, parent ID, template name, page count (for paginated documents), and timestamps.

This does NOT return field values — for those, call get_field_values. This does NOT return document content — for that, call get_document_edoc (mode="text" for extracted text, mode="bytes" for the raw file).

Args: entry_id: Integer entry ID.

Returns: EntryDetail (id, name, entry_type, parent_id, full_path, template_name, page_count, is_electronic_document, extension, creation time, last modified time).

On failure: returns {"mode": "error", "error": <slug>, "entry_id": <int>, ...}. Common slugs: not_found, auth_failed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entry_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

With no annotations, description carries full burden. Clearly states it returns metadata only and not field values or content. Describes error slugs. Minor lack of mention of auth requirements, but acceptable for a read operation.

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?

Description is well-structured with clear sections, bullet points, and explicit 'does NOT' statements. Slightly verbose but every sentence adds value.

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 output schema exists, description provides enough context: lists return fields, covers error handling, and explains what the tool does not do. Complete for a single-parameter metadata fetch tool.

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?

Only one parameter entry_id. Description adds context: 'Integer entry ID' and where to obtain it (from search, list_folder, etc.), which adds value beyond schema's type and required declaration.

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 'Fetch metadata for a single entry by ID' with specific verb and resource. Distinguishes from siblings by noting alternative tools for field values and document content.

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 (once you have an entry ID from specific tools) and what it does NOT return, with clear pointers to alternatives (get_field_values, get_document_edoc). Includes return format and error handling.

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