Skip to main content
Glama
Cresca MCP Server

Cresca MCP Server

List templates

list_templates
Read-onlyIdempotent

Retrieve all email templates in an account, newest first, including drafts and non-API-ready templates; use pagination to browse results and inspect current draft versus published version.

Instructions

GET /templates. Lists every template in the account, newest first, including drafts and templates not set up for the API (status "draft", alias null). Content fields show the current draft; version is the published version sends use. Pagination: while has_more is true, pass the last item's id as after. Needs a full-access key. Read-only.

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
afterNoA template id. Returns templates older than it (the next page).
limitNoNumber of templates to return, 1 to 100. Default 20.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and the one-word "Read-only" merely echoes them. Beyond that the description adds genuinely useful context: it requires a full-access key, ordering is newest first, drafts are included, and it explains that content fields reflect the draft while version is the published version used by sends.

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?

Front-loaded with the endpoint and the core behavior, then pagination, then auth. Four dense sentences with no filler; each one carries a distinct operational fact.

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?

For a two-optional-parameter list tool with no output schema, the description covers ordering, draft inclusion, pagination loop mechanics, field meaning (content vs version) and auth requirements. The only modest gap is it doesn't hint at the response envelope beyond has_more.

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 both `after` and `limit` are already documented in the schema. The description's pagination note (pass the last item's id as `after` while has_more is true) restates and slightly clarifies the loop, but it never mentions `limit`, so it adds only marginal meaning.

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 concrete verb and resource ("Lists every template in the account") plus scope details: newest first, includes drafts and API-unconfigured templates. An agent can immediately distinguish this full-list operation from the singular get_template sibling.

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?

Usage is implied by the scope statement (use this to see all templates including drafts, status "draft" with alias null), but there is no explicit when-to-use vs. when-not guidance and no named alternative such as get_template or list_emails. The reader must infer the routing rule.

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