Skip to main content
Glama

list_decorations

Filter your saved decoration library by content type, category, or tag to find reusable designs.

Instructions

List all saved decorations in the library.

        Browse the decoration library to find reusable decorations.
        Filter by content type, category, or tag.

        :param content_type: Filter by type — ``photo``, ``svg``, ``qr``,
            ``text``, ``procedural_texture``, ``ai_texture``
            (empty = show all).
        :param category: Filter by category — ``surface`` (photo/svg/qr/text)
            or ``texture`` (procedural/AI textures).  Empty = show all.
        :param tag: Filter by tag (empty = show all).
        :returns: Dict with decoration count and list.

        This is the decoration LIBRARY: keyed by name, and it ADAPTS —
        each recorded success stores proven settings for THAT material,
        so applying picks the depth and mode your prints proved for
        whatever you are printing in now.  It keeps no version history.

        Kiln's other kind of saved decoration is a decoration PRESET
        (kiln-pro; what the web's /decorations pages show): keyed by an
        id because it has versions, branches and signed releases, and
        applied at the exact settings its version recorded rather than
        adapting to the material.  Listed by ``list_decoration_presets``,
        applied by ``apply_decoration_preset``.  The library adapts, the
        preset remembers — if what you want isn't here, look there.
        

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tagNo
categoryNo
content_typeNo
Install Server

TDQS

A4.7/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full disclosure burden. It does so well by revealing that the library is keyed by name, always adapts to proven settings, and has no version history. It also states the return shape (dict with decoration count and list), which gives useful behavior beyond a simple 'list' label.

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 longer than a simple tool needs, but nearly every section earns its place: the intro sentence, filter documentation, return info, and the critical distinction from presets. It is thoughtfully structured with clear paragraphs and front-loaded intent. A minor redundancy exists between 'List all' and 'Browse...', but it does not detract.

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?

The tool has only three optional filter parameters, no output schema, and no annotations, so the description is the only practical guidance. It covers the purpose, parameter semantics, return value, and a key domain distinction (library vs preset) that materially affects tool selection. This is fully sufficient for an agent to invoke the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% because the input schema only has bare string properties with default empty values. The description fills this entirely by documenting all three filter parameters, including valid content_type values ('photo', 'svg', 'qr', 'text', 'procedural_texture', 'ai_texture') and category meanings. This is more helpful than typical schema descriptions.

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 'List all saved decorations in the library,' naming the exact resource and action. It explicitly contrasts this with decoration presets and points to list_decoration_presets/apply_decoration_preset, making it easy to distinguish from similar catalog-style tools.

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 this is for browsing the decoration library, with filters, and adds a when-not-to-use directive: 'if what you want isn't here, look there' (to presets). It also explains the conceptual difference between library and preset, so an agent can select the right tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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/codeofaxel/kiln'

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