Skip to main content
Glama
Cresca MCP Server

Cresca MCP Server

Delete template (permanent)

delete_template
DestructiveIdempotent

Permanently deletes a Cresca email template by ID or alias, including its version history; use only after user confirmation because removal cannot be undone.

Instructions

DELETE /templates/:id. PERMANENTLY deletes a template, by id or alias, and its version history, from the API and the Cresca app. This cannot be undone. Emails that still reference it fail with 404 not_found, so confirm with the user first. 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": "delete_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 beyond the annotations by disclosing that version history is destroyed, the action is irreversible, downstream emails referencing the template return 404 not_found, and elevated auth (full-access key) is needed — none of which is conveyed by destructiveHint alone.

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 strongest fact (permanent deletion), then layers consequences and prerequisites. Every sentence carries information; nothing is padded.

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?

For a one-parameter destructive tool with no output schema, the description covers scope, irreversibility, side effects on dependent emails, and auth requirements — everything an agent needs before invoking it.

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 is already documented as 'The template id or alias'. The description restates 'by id or alias' without adding format, encoding, or lookup-order details, so baseline 3 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 precise verb and resource ('PERMANENTLY deletes a template, by id or alias, and its version history') plus the underlying route DELETE /templates/:id, which cleanly separates it from get_template, update_template and publish_template.

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 clear operational conditions: confirm with the user first, and a full-access key is required. It does not name alternate tools (e.g. update_template for non-destructive edits), but for a terminal delete there is no real substitute, so the missing exclusion is minor.

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