Skip to main content
Glama
Pirate Ship MCP Server

Pirate Ship MCP Server

List email templates

list_email_templates
Read-onlyIdempotent

Lists tracking email templates sent to label recipients, returning IDs, names, subjects, sender and reply-to details, BCC addresses, and HTML bodies; use an ID to update or delete a template.

Instructions

List the templates of the tracking emails sent to label recipients.

Returns every template with its id, name, subject, sender name, reply-to email, BCC address and HTML body with placeholders such as [Tracking #]; default marks the one used for new labels. Use the id in update_email_template or delete_email_template. Whether emails go out at all and when is in get_tracking_email_settings.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description still adds real value by enumerating the returned fields, explaining the 'default' marker for new labels, and noting the [Tracking #] placeholder format in the HTML body. 'Returns every template' implicitly discloses that no pagination or filtering applies, though it could say so outright.

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?

Three short sentences, each doing distinct work: what it lists, what comes back, and where to go next. Purpose is front-loaded and nothing is repeated from the title or annotations.

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?

With no output schema, the description carries the return-value burden and does so by listing every field plus the default flag. Combined with the annotations and the sibling routing, an agent has everything needed to call and interpret this tool.

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?

The tool takes zero parameters, so the schema imposes no documentation burden and the baseline of 4 applies. The description correctly adds no parameter noise and instead spends its words on return shape.

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 ('List the templates of the tracking emails sent to label recipients') and scopes it to the tracking-email domain, which separates it from the many other list_* siblings. An agent knows exactly what collection is being read without opening the schema.

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?

Explicitly routes downstream work: 'Use the id in update_email_template or delete_email_template' names the follow-on tools, and 'Whether emails go out at all and when is in get_tracking_email_settings' draws a clear boundary against a sibling an agent might otherwise confuse this with. Both when-to-use-next and when-not-to-use-this are covered.

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