Skip to main content
Glama

List templates

list_templates
Read-onlyIdempotent

List the templates the user saved in My Templates, and those of the team they belong to: id, name, owner ("personal" or "team"), slide_count, theme_id, source, updated_at, version (the published version; also as published_version) and has_draft (the template has unpublished changes). Team templates also have created_by, review_state and unresolved_feedback (pin comments waiting). Use it to find a template the user refers to, and to read slide_count before appending with update_template. Needs an API key; works on any plan.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, closed-world, non-destructive behavior, so the description only needs to add what they don't cover. It does: the exact returned fields, the meaning of has_draft ('unpublished changes'), team-only fields, unresolved_feedback semantics, and the API key requirement. Pagination/result limits are not mentioned, which keeps it below 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first clause, followed by the field inventory with inline glosses for non-obvious fields (version/published_version, has_draft), then usage and prerequisites. Every sentence carries information, and nothing is repeated from annotations.

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 inline field list and the glosses on has_draft and unresolved_feedback are exactly what an agent needs to interpret results. Auth and plan requirements are stated, and the workflow link to update_template covers the main follow-on action.

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?

The tool takes no parameters, so there is no parameter semantics to explain; the baseline for a zero-parameter schema is 4. The description correctly invests its space in output fields instead.

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 the templates') and precisely scopes it to My Templates plus team templates. The enumerated return fields (id, name, owner, slide_count, theme_id, source, updated_at, version, has_draft) make clear this is a discovery/list operation distinct from a single-template fetch like get_template.

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?

Explicitly says when to use it: 'to find a template the user refers to' and 'to read slide_count before appending with update_template', naming the downstream sibling. It also states prerequisites ('Needs an API key; works on any plan'), which removes a common selection blocker.

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