Skip to main content
Glama

List templates

templates_list
Read-onlyIdempotent

Lists the email templates and, for each, the blocks_schema (JSON Schema for heading, body_md, cta_text, cta_url, image_url, image_alt and sections). Free and read only. Pick a template here before campaign_draft and fill only the blocks its schema accepts. Requires API key scope: read.

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": "templates_list"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so "Free and read only" is largely redundant. The description does add real value beyond annotations by disclosing the return payload structure (blocks_schema and its field set) and the read-scope requirement, though it omits pagination or whether templates are custom vs. built-in.

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 verb and resource, then the return shape, then the workflow instruction. Minor waste in "Free and read only," which restates the readOnlyHint annotation.

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?

No output schema exists, so the description carries the burden of explaining the return value — and it does, enumerating the blocks_schema fields an agent must populate. Combined with the downstream campaign_draft instruction and auth scope, nothing needed to call it correctly is missing.

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 zero parameters (empty object schema, 100% coverage), so the baseline is 4 and no parameter documentation is owed. The description correctly implies the listing takes no filters.

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?

Specific verb + resource ("Lists the email templates") plus disclosure of what each item contains (blocks_schema covering heading, body_md, cta_text, cta_url, image_url, image_alt, sections). That level of detail clearly separates it from campaigns_list or surveys_list siblings, which return different resources.

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?

Gives an explicit workflow: "Pick a template here before campaign_draft and fill only the blocks its schema accepts," naming the downstream sibling and the constraint on which fields to populate. It also states the auth prerequisite (read scope), so an agent knows both ordering and access requirements.

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