Skip to main content
Glama
Cresca MCP Server

Cresca MCP Server

Update template draft

update_template
DestructiveIdempotent

Updates a template's draft by overwriting only the fields you send; live email keeps using the published version until you publish it. Send alias: null to remove it; requires a full-access key.

Instructions

PATCH /templates/:id. Changes a template's DRAFT, overwriting the fields you send (send only the ones to change; same formats as create_template). Live email keeps using the published version until publish_template is called. Send alias: null to remove the alias. Sending html replaces a visual-editor design with plain HTML. Needs a full-access key.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe template id or alias.
fromNoDefault sender.
htmlNoNew HTML body.
nameNoNew name, up to 120 characters, unique in the account.
textNoPlain-text version.
aliasNoNew alias, or null to remove it.
subjectNoDefault subject.
reply_toNoDefault Reply-To address.
variablesNoReplaces all variable definitions (up to 50).
preview_textNoPreview text, up to 500 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare destructive/idempotent flags; the description adds the semantics that matter: PATCH-style merge (only sent fields are overwritten), draft-vs-live isolation, null-to-clear behavior, the side effect that html discards a visual-editor design, and the full-access key requirement. That is substantial disclosure beyond the structured fields.

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?

Five short sentences, each carrying a distinct constraint, front-loaded with the route and the draft-only scope. Nothing is redundant with the title or schema.

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 10-parameter mutation with no output schema, it covers the risky behaviors (partial overwrite, draft isolation, destructive html swap, auth level) well. It does not describe the response payload or what happens to unpublished changes on validation failure, which are minor residual gaps.

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?

Schema coverage is 100%, so baseline is 3; the description adds meaning beyond it by explaining that html replaces a visual-editor design with plain HTML and that field formats follow create_template. Null-removal for alias is stated in both places, so it earns less credit.

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 ("Changes a template's DRAFT") and bounds the scope precisely — draft only, live email unaffected. It is clearly distinguishable from create_template (format reference) and publish_template (the step that makes changes live).

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?

Explicitly routes the agent: use this for draft edits, use publish_template to make changes live, and follow create_template's formats for field values. No explicit "do not use this for X" exclusion, so it stops short of a full 5, but the alternative-routing is strong.

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