Skip to main content
Glama
Cresca MCP Server

Cresca MCP Server

Retrieve template

get_template
Read-onlyIdempotent

Retrieve an email template by ID or alias to review its draft content, publication status, and published version for editing or send preparation.

Instructions

GET /templates/:id. Returns a template by id or alias. html, subject and the other content fields show the current DRAFT; status is "draft" until the first publish, then "published"; version is the published version that sends use. Needs a full-access key. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe template id or alias.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered, yet the description still adds real behavioral value. It explains that content fields return the DRAFT while status/version reflect publication state, and that a full-access key is required — both non-obvious facts an agent would otherwise get wrong. It stops short of describing failure modes or pagination, hence not 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.

Conciseness4/5

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

It is front-loaded with the endpoint and the core action, then layers the draft/published/version semantics compactly in one sentence. The semicolon-chained phrasing is dense but every clause carries distinct information; only the redundant "Read-only" tail repeats what the annotations already say.

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 one-parameter read with no output schema, the description supplies the essential missing context: that returned content is draft content, what status and version mean, and the key-level required. Nothing critical about calling it correctly is missing, though error handling and the shape of the response remain implicit.

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 coverage is 100% and the single parameter's schema description already says "The template id or alias." The description's "by id or alias" restates that without adding format, lookup, or ambiguity-resolution detail, so it earns no premium over the schema baseline.

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?

"Returns a template by id or alias" is a specific verb plus resource, and the GET /templates/:id line pins down the operation unambiguously. It does not explicitly name how it differs from siblings like update_template or publish_template, but the retrieval framing is clear enough that no confusion is plausible.

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 only implied: fetch a template when you have its id or alias. There is no explicit when-to-use versus list_templates or get_email, and no stated exclusions or error behavior for unknown ids. The access-key prerequisite is stated, which is useful, but routing guidance is absent.

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