Skip to main content
Glama

List Asset Layouts

hudu_list_asset_layouts
Read-onlyIdempotent

List asset layouts in Hudu to inspect the templates behind asset types, including custom fields, icons, and settings. Discover layout names and field labels before creating or updating assets.

Instructions

List asset layouts in Hudu. An asset layout is the template behind an asset type: its icon and colour, whether its assets can hold passwords, photos, comments and files, and the set of custom fields every asset of that type carries. Layouts are instance-wide rather than per-company. Field definitions can be set when a layout is created; the documented shape for changing them afterwards contradicts the shape creation accepts, so this server does not expose field edits on update. There is no delete endpoint for layouts — set active: false to retire one.

Read this before writing any asset: the fields array on each layout gives the labels that hudu_create_asset and hudu_update_asset expect as custom_fields keys, in snake_case. This endpoint documents page but no page_size, so pages come back at the server's own size.

Returns an object with items plus pagination facts. Note that the Hudu API returns no total count for any collection, so page_was_full is the only honest signal that more records exist — read pagination_note before concluding a list is complete.

Operation class: Read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoMatch against the layout name, e.g. "Server".
pageNo1-based page number. Hudu has no cursor or offset — only pages.
slugNoURL slug, if you already know it.
fieldsNoReturn only these top-level fields on each record. Use it to keep large lists small — e.g. ["id","name","company_id"]. Unknown field names are ignored.
updated_atNoISO-8601 range as "start,end". Either side may be omitted — "2026-01-01T00:00:00Z," means everything changed since that moment.
response_formatNoOutput shape. 'json' (default) is compact and machine-readable; 'markdown' is easier for a person to read but larger.json
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds substantial behavioral context: layouts are instance-wide, field edit semantics are intentionally not exposed, pagination is server-sized, and the API returns no total count so page_was_full is the only reliable pagination signal. These go far beyond annotation defaults.

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?

The description is long but every sentence carries crucial information. It front-loads the core purpose, then organizes caveats into logical paragraphs covering layout properties, update limitations, pagination behavior, and output shape. No fluff, no redundancy.

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?

With no output schema, the description takes on the full burden of explaining return values ('items plus pagination facts'), pagination semantics ('page_was_full', 'pagination_note'), and API quirks (no total count). It also explains how this tool feeds into asset creation/update, making it self-sufficient for correct invocation.

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 baseline is 3. The description adds value by explaining the page parameter's server-controlled page size and the deeper meaning of the fields array in relation to hudu_create_asset/hudu_update_asset, but most parameter semantics are already well-documented in the schema.

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 opens with the specific verb+resource ('List asset layouts in Hudu') and elaborates on what an asset layout is, making the tool's purpose unmistakable. It clearly differentiates from sibling tools like hudu_get_asset_layout by focusing on the collection-level list operation.

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?

Provides explicit guidance on when to use this tool: 'Read this before writing any asset' to determine custom_fields keys for create/update. Also states exclusions—no delete endpoint (use active:false) and no field edits on update—and explains pagination caveats so the agent knows what to expect.

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/ZenixSolutions/hudu-mcp'

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