Skip to main content
Glama

List templates

list_templates
Read-onlyIdempotent

Lists public template catalog summaries from Gateway, filterable by platform, role, density, and canvas preset, to help you find suitable carousel templates.

Instructions

List public template catalog summaries from Gateway (filterable by platform, role, density, canvasPreset). Alternatives: Use get_template to inspect specific slot requirements. Read-only catalog query.

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

Input Schema

NameRequiredDescriptionDefault
qNoSearch term matching template name or description.
allNoFetch all matching templates across pages.
limitNoMax items per page.
rolesNoNarrative role filter: hook | value | rehook | cta
cursorNoPagination cursor from previous nextCursor.
localeNoLanguage/locale code (e.g. en, zh-CN).
densityNoDensity filter: sparse | normal | dense
platformsNoPlatform filter: tiktok | linkedin | instagram | threads | xiaohongshu
canvasPresetNoAspect ratio preset (e.g. 9:16, 4:5, 1:1, 3:4).
contentFamilyNoContent family filter.
requiresImageNoFilter templates that require an image slot.
contentArchetypesNoContent archetypes list.

Output Schema

NameRequiredDescriptionDefault
templatesNoTemplate summaries.
nextCursorNoCursor for next page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changedv0.1.17
    • addedInput schema / properties / all / description
      Added value: +"Fetch all matching templates across pages."
    • addedInput schema / properties / canvasPreset / description
      Added value: +"Aspect ratio preset (e.g. 9:16, 4:5, 1:1, 3:4)."
    • addedInput schema / properties / contentArchetypes / description
      Added value: +"Content archetypes list."
    • addedInput schema / properties / contentFamily / description
      Added value: +"Content family filter."
    • addedInput schema / properties / cursor / description
      Added value: +"Pagination cursor from previous nextCursor."
    • addedInput schema / properties / density / description
      Added value: +"Density filter: sparse | normal | dense"
    • addedInput schema / properties / limit / description
      Added value: +"Max items per page."
    • addedInput schema / properties / locale / description
      Added value: +"Language/locale code (e.g. en, zh-CN)."
    • addedInput schema / properties / platforms / description
      Added value: +"Platform filter: tiktok | linkedin | instagram | threads | xiaohongshu"
    • addedInput schema / properties / q / description
      Added value: +"Search term matching template name or description."
    • addedInput schema / properties / requiresImage / description
      Added value: +"Filter templates that require an image slot."
    • addedInput schema / properties / roles / description
      Added value: +"Narrative role filter: hook | value | rehook | cta"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "nextCursor": {
      +      "description": "Cursor for next page.",
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "templates": {
      +      "description": "Template summaries.",
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observedv0.1.13

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds value beyond them by scoping results to the 'public' catalog and signaling that entries are 'summaries', which tells the agent to expect lightweight records. It omits pagination behavior (cursor/limit/all), which the schema carries instead.

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?

Three short sentences, front-loaded with the action and scope, with the alternative routing placed before the closing note. The final sentence 'Read-only catalog query' largely restates the readOnlyHint annotation, making it the only near-redundant element.

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?

With an output schema present, return values need no explanation, and the 12-parameter schema is fully self-documenting. The description supplies scope, the browse-vs-inspect alternative, and the public-catalog constraint, leaving only pagination semantics unmentioned at the description level.

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%, so all twelve parameters are documented in the schema itself. The description echoes four of the filter categories (platform, role, density, canvasPreset) but adds no syntax or defaulting detail beyond what the schema provides, so the baseline of 3 applies.

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?

States a specific verb and resource ('List public template catalog summaries from Gateway') plus the filter dimensions, and explicitly frames the result as summaries rather than full templates. An agent can distinguish it from get_template without opening either schema.

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

Usage Guidelines4/5

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

Names the sibling alternative 'get_template' with the condition that selects it ('to inspect specific slot requirements'), giving a clear browse-vs-inspect split. It does not state explicit when-not conditions for the list itself, but the routing guidance is concrete.

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