Skip to main content
Glama

list_link_definitions

Retrieve entry-link type definitions from the repository, providing linkTypeId, sourceLabel, and targetLabel needed for set_links.

Instructions

List the entry-link type definitions available on this repository.

Use before calling set_links — you need a linkTypeId from this listing to construct a valid link. Each link type is directed: it has a sourceLabel (how the relationship reads from the source entry) and a targetLabel (how it reads from the target).

Args: max_results: Page size (default 25). skip: 0-indexed offset for pagination. summary_only: If True, return only {count, names}.

Returns: Server's raw OData listing with value. Each item has linkTypeId, sourceLabel, targetLabel, and linkTypeDescription. Common defaults include "Supersedes" / "Superseded by" and "Attachment" / "Message".

On failure: returns {"mode": "error", "error": <slug>, ...}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
max_resultsNoPage size (default 25, capped by LF_MAX_RESULTS_CEILING).
skipNo0-indexed offset for pagination through large repositories.
summary_onlyNoWhen True, return only {count, names} instead of the full OData listing — useful for 'what's available?' lookups that would otherwise return 30-50 KB of definition payload.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations provided, so description carries full burden. It describes the return format (OData listing with value, fields), behavior of summary_only parameter (return {count, names}), and failure mode (error object). This is comprehensive for a read-only 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?

Well-structured with sections for purpose, usage, args, returns, and failure. Front-loaded with purpose. Could be slightly more concise but is efficient and clear.

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 tool's simplicity (3 params, no required, with output schema), the description covers all necessary aspects: usage, pagination, summary mode, return fields, and failure. It even includes common examples of link types, making it highly complete.

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% with descriptions, but the description adds value by explaining defaults (max_results default 25, skip default 0) and the pragmatic use of summary_only to avoid heavy payloads. This contextual information goes beyond what the schema provides.

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 'List the entry-link type definitions available on this repository,' providing a specific verb and resource. It distinguishes itself from sibling listing tools by specifying 'entry-link type definitions' and further explains directed link types with source and target labels.

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

Usage Guidelines4/5

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

Explicitly states 'Use before calling set_links — you need a linkTypeId from this listing to construct a valid link,' providing clear context for when to use. Does not explicitly exclude alternatives, but the direct reference to set_links makes the use case obvious.

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