Skip to main content
Glama

List themes

list_themes
Read-onlyIdempotent

Search or filter the theme catalog. Returns metadata and key colors only, not the full CSS. With an API key, the user's own saved themes (My Themes, id "custom:...") come last with custom: true; their ids work anywhere a theme id does.

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_themes"
  }
}

Input Schema

NameRequiredDescriptionDefault
moodNoMood keyword to filter themes by, e.g. "minimal" or "bold". Omit for all themes.
schemeNoOnly themes with this color scheme. Omit for both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / mood / description
      Added value: +"Mood keyword to filter themes by, e.g. \"minimal\" or \"bold\". Omit for all themes."
    • addedInput schema / properties / scheme / description
      Added value: +"Only themes with this color scheme. Omit for both."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish the read-only, idempotent, closed-world safety profile, so the description only needs to add context beyond that — and it does: the return payload is truncated to metadata and key colors rather than full CSS, and an API key changes the result set by appending the user's own themes with custom: true. Ordering ('come last') and the id-compatibility guarantee are behavioral details an agent cannot get from annotations or schema.

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?

Two sentences, no waste, and the scope statement is front-loaded before the return-value caveat and the API-key nuance. Every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must characterize the return value — it does so by naming the payload limits (metadata and key colors, not full CSS) and the custom: flag on saved themes. Minor gaps remain around ordering of non-custom themes and pagination, but nothing essential to a correct call is missing.

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

Parameters3/5

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

Schema description coverage is 100% and both parameters carry their own enum/omission guidance, so the baseline is 3. The description adds no extra meaning about mood matching semantics or scheme behavior, though it does clarify the non-parameter notion of 'custom:...' ids.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence gives a precise verb and resource ('Search or filter the theme catalog') and the second sentence implicitly separates it from the richer get_theme by noting it returns metadata and key colors only, not the full CSS. It never names get_theme or list_templates explicitly, so the sibling differentiation is inferential rather than stated.

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

Usage Guidelines3/5

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

It conveys when this tool is the right shallow choice ('not the full CSS') and explains that saved themes appear last with custom: true and that their ids work anywhere a theme id does, which is genuinely useful downstream routing. However, there is no explicit guidance on choosing it over get_theme or list_templates, and filtering behavior is left to the schema.

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