Skip to main content
Glama

Postcard campaign templates and jobs

spur_manage_mail_campaign
Destructive

Manage campaign-specific templates, stage owner recipients, inspect jobs and summary. Staging verifies addresses and can spend personalization Actions; requires approval. Dispatch uses a separate mail preview and token. These templates are distinct from normal direct-mail templates.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Goes meaningfully beyond the annotations: staging verifies addresses, can spend personalization Actions (a real cost), and requires approval; dispatch requires a separate preview and token. The annotations already flag destructiveHint and openWorldHint, so the added cost/approval/preview-sequencing context is the valuable part. It does not state what delete_template destroys or whether staging is reversible, keeping it at 4.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the resource and operations, then the risk/approval constraints. Nothing is padded, though 'inspect jobs and summary' is compressed to the point of being slightly cryptic about what a summary contains.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-action destructive dispatcher with no output schema, the description covers staging, jobs, summary and template distinctness but never addresses the create/update/delete template actions or what a staged job's lifecycle looks like. An agent can orient itself but must read the oneOf schema to learn the available actions and the confirm requirement.

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 description coverage is 100% and the oneOf branches constrain action with const values, so the schema carries most of the burden. The description adds a little meaning — 'stage owner recipients' maps to owner_ids, and the approval note reinforces the confirm parameter. It does not clarify template_id vs campaign_id roles, pagination, or the optional redirect_id/return_address_id.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific domain (campaign-specific postcard templates) plus the operations: manage templates, stage owner recipients, inspect jobs and summary. It also explicitly distinguishes these templates from normal direct-mail templates. It falls short of 5 because the umbrella verb 'manage' obscures that this is an 8-action dispatcher whose actions (templates/template/create_template/update_template/delete_template/stage/jobs/summary) are never enumerated.

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

Usage Guidelines3/5

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

Implies the workflow: stage first (with approval), then dispatch via a separate mail preview and token, which points the agent toward the preview/dispatch siblings. However, it never names those siblings, never says when to use this tool's template actions versus spur_create_postcard_template / spur_update_postcard_template / spur_list_postcard_templates, and gives no exclusions. Guidance is inferable but not explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources