Skip to main content
Glama
Cresca MCP Server

Cresca MCP Server

Publish template (changes live email)

publish_template
Destructive

Publishes a template’s current draft as a new live version; all future sends use it, so confirm before updating a template already in use.

Instructions

POST /templates/:id/publish. Copies the current draft (HTML, text, subject, default sender, Reply-To, preview text and variables) into a new published version. EVERY email sent with this template from then on uses the new version, so confirm with the user before publishing a template that is in use. Undeclared placeholders are added as string variables without a fallback. Earlier versions stay in the app's version history. Needs a full-access key. Returns { id, version }.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe template id or alias.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

Goes well past the annotations: it discloses the live-impact scope ('EVERY email sent with this template from then on uses the new version'), the side effect on undeclared placeholders (added as string variables without a fallback), the reversibility story (earlier versions stay in version history), and the auth requirement (full-access key). The annotations flag destructiveHint/openWorldHint, and the description supplies the concrete consequences behind those flags.

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-loads the endpoint and the core action, then layers consequence, edge case, and auth in short declarative sentences. No filler; each clause carries distinct operational information.

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?

Despite having no output schema, it explicitly describes the return shape as { id, version }, and it covers the mutation's blast radius, version history behavior, and permission level. For a one-parameter publish action, nothing an agent needs to call it safely is missing.

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?

Only one parameter, and the schema already documents it at 100% coverage as 'the template id or alias.' The description merely echoes the path parameter as :id and adds no lookup-format or alias-resolution detail beyond the schema, so baseline 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 (publish a template via POST /templates/:id/publish) and then enumerates exactly what gets copied into the published version. The draft-versus-published-version framing is what separates it from plain draft editing like update_template, so an agent can select it without inspecting siblings.

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?

Gives an explicit precondition-style caution: 'confirm with the user before publishing a template that is in use,' which is the key decision rule for this action. It does not name an alternative tool or spell out when-not-to-publish at all (e.g. draft not ready), so it stops short of full routing guidance.

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