Skip to main content
Glama

List layouts

list_layouts
Read-onlyIdempotent

Search or filter the layout catalog to find a specific layout. Returns metadata only, no HTML. Each entry has position (opener/middle/closer: its role in a deck), when_to_use and when_not_to_use: read them to check the layout fits the content before choosing it. Filter by position to fill a slot of the story, e.g. position "closer" for the last slide. Also the tool for "what is new", "any new layouts?", "what got added since last month" - pass since and it returns only what landed after that date. If the user asked for a whole deck rather than one slide, call suggest_deck first instead of this.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_layouts"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of description, best_for and when_to_use / when_not_to_use. Pass the language the user is writing in.ko
limitNoMaximum number of layouts to return (1 to 150). Default 30.
queryNoWords that must all appear in the name, description, best_for, when_to_use or content type.
sinceNoISO date (YYYY-MM-DD). Only layouts added after it. Use for "what is new" questions; if the user gave no date, a month back is a sensible default.
categoryNoLayout category id to filter by, e.g. a category from the catalog. Omit for all categories.
positionNoThe slide's role in a deck: opener = cover, middle = content, closer = ending (summary, CTA, thanks). Use it to fill each part of the story: first slide with opener, last with closer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Layout category id to filter by, e.g. a category from the catalog. Omit for all categories."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of layouts to return (1 to 150). Default 30."
  2. Changed3 schema fields changed
    • addedInput schema / properties / lang
      Added value: +{
      +  "default": "ko",
      +  "description": "Language of description, best_for and when_to_use / when_not_to_use. Pass the language the user is writing in.",
      +  "enum": [
      +    "ko",
      +    "en"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / position
      Added value: +{
      +  "description": "The slide's role in a deck: opener = cover, middle = content, closer = ending (summary, CTA, thanks). Use it to fill each part of the story: first slide with opener, last with closer.",
      +  "enum": [
      +    "opener",
      +    "middle",
      +    "closer"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / query / description
      Added value: +"Words that must all appear in the name, description, best_for, when_to_use or content type."
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

The annotations already state readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds value beyond them: 'Returns metadata only, no HTML', which tells the agent it must render or fetch separately before showing a slide, and it names the fields each entry carries (position, when_to_use, when_not_to_use). It does not mention pagination or how results are ordered, which keeps it from a 5.

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 front-loaded with what the tool returns and how to read the entries, then the filters and alternatives. It is longer than a minimal definition, and the position guidance is partly repeated between the filter sentence and the enum explanation, but every sentence still carries useful routing or usage information.

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?

Six optional parameters, two enums and no output schema, yet the description covers what is returned (metadata, no HTML), the fields in each entry, the filters and the sibling to use for an adjacent task. An agent has what it needs to call it correctly and to know when a result is not enough.

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, but the description goes further: it explains the position enum by showing how to use it on a real request ('position "closer" for the last slide') and gives practical guidance for `since`, such as defaulting to a month back when no date is given. Those additions make the parameters easier to use than the schema 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 gives a specific verb and resource ('Search or filter the layout catalog') and clearly separates this tool from close siblings: `get_layout` for one layout and `suggest_deck` for a full deck. The agent can tell which tool to pick without opening the schemas.

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?

It states concrete usage modes: filter by position to fill a deck slot, pass `since` for 'what is new' questions, and call `suggest_deck` first if the user wants a whole deck rather than one slide. Both the when and the when-not are explicit, along with the alternative to use instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources