Skip to main content
Glama
Pirate Ship MCP Server

Pirate Ship MCP Server

Delete email template

delete_email_template
Destructive

Permanently deletes a tracking email template from an account, removing it for good without changing tracking emails already sent.

Instructions

Delete one tracking email template from the account.

Removes the template for good; it cannot be restored. Tracking emails already sent are not changed. To change a template's text instead, use update_email_template. Returns the deleted template's id.

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": {
      "template_id": "<template_id>"
    },
    "name": "delete_email_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
template_idYesid from list_email_templates.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark the tool as destructive, but the description adds critical context: removal is permanent and cannot be restored. It also clarifies that already-sent tracking emails are unaffected and states what is returned, which goes beyond the structured annotations.

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?

The description is four short, front-loaded sentences with no wasted language. The irreversible warning, alternative, and return value are all presented efficiently.

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 simple one-parameter destructive operation with rich annotations and full schema coverage, the description supplies everything an agent needs: permanence, effect on sent emails, the relevant alternative, and the return value.

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?

The input schema has 100% description coverage and already documents template_id as the id from list_email_templates. The description does not add any further meaning about the parameter, so the baseline of 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?

The description states a specific verb and resource: deleting one tracking email template from the account. It clearly distinguishes this from update_email_template by naming that sibling for text changes, and the scope is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly names the alternative to use when changing template text: update_email_template. The irreversibility warning also makes clear that this tool is for permanent removal, leaving no ambiguity about when to choose it.

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