Playbook

Get page elements catalog

get_page_elements_catalog

Read-only

The vocabulary for designing a board's published page — read it BEFORE publishing with a template or writing any page element. Returns: templates (the valid template ids for publish_board, each with its display name, default background/typography and the slots it mounts itself — a floor, not an inventory), element_types (the names of every element type), enum_sets, background_colors and typographies (the values update_page_settings accepts), operations (the argument map for apply_page_operations), and limits. The same for every workspace. The props of the element types are large (~40 KB together), so they come back only for the types named in the element_types argument, under elements: each type with the camelCase props it accepts, flagged html, url, asset_token or dead — a dead prop is stored but no longer rendered. A designed page is built from sections (up to 3 columns, each holding note and asset rows) under a banner hero, and its look comes from the style prop on notes and assets — gradients, cards, shadows, tilts, big type; read style on note before relying on color. There is no carousel or slideshow element: present a deck as ordered sections, or as a grid with horizontalView and autoScroll.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`element_types`	No	Element types to return the props of, under `elements` (e.g. ['banner', 'button']). Without it the response lists the type names and no props. An unknown type is refused with the valid list.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 5, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

removedInput schema / properties / context

Removed value: -{
-  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
-  "type": "string"
-}

changedInput schema / properties / element_types / description

Previous value: -"Return only these entries of `elements` (e.g. ['banner', 'button']). Everything else is always returned. An unknown type is refused with the valid list."New value: +"Element types to return the props of, under `elements` (e.g. ['banner', 'button']). Without it the response lists the type names and no props. An unknown type is refused with the valid list."

removedInput schema / required
```
Removed value: -[
-  "context"
-]
```

First observedOct 2, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already establish readOnly/openWorld=false, and the description adds substantial operational context beyond them: the ~40 KB props payload is only returned for types named in the argument, dead props are stored but not rendered, and the catalog is identical for every workspace. It also discloses a design constraint (no carousel element; use sections or a grid with horizontalView/autoScroll).

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?

It is dense and long, but front-loaded with the core purpose and downstream consumers before the return-value detail; nearly every sentence carries actionable information, though the style/carousel guidance could be trimmed slightly.

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 fully carries the burden of explaining return structure, the conditional props behavior, and the element taxonomy (sections, columns, banner, notes/assets, style prop), leaving nothing essential for correct invocation unstated.

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% and the schema description already explains the element_types argument's effect and unknown-type refusal, so baseline is 3. The description adds the ~40 KB size hint that matters for request planning, which is a genuine incremental detail over 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 defines the tool as 'the vocabulary for designing a board's published page' and then enumerates exactly what it returns (templates, element_types, enum_sets, background_colors, typographies, operations, limits), making its distinct role unmistakable against siblings like get_page_layout or publish_board.

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 an explicit imperative timing rule — 'read it BEFORE publishing with a template or writing any page element' — and ties its outputs to the sibling tools that consume them (publish_board, update_page_settings, apply_page_operations), so an agent knows precisely when this must be called.

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

All Playbook tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?