Skip to main content
Glama

save_email_campaign_draft

Save an email campaign draft for review in Cockatoo. Use revision 0 for a new draft or the current revision to update it.

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>",
      "revision": "<revision>",
      "value": "<value>"
    },
    "name": "save_email_campaign_draft"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
valueYes
revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the safety profile is covered and the description only needs to add context. It does add that the result is a draft held for review and that revisions gate updates, but it never says what happens on a stale/mismatched revision — the key behavioral question given idempotentHint=false — nor whether saving overwrites prior content.

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?

Two sentences, front-loaded with the action and resource, then the revision rule. No filler, no restatement of the tool name, and nothing redundant with the annotations.

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 a mutation tool with a nested 50-item block array, no output schema, and zero schema descriptions, the definition covers the concurrency mechanism but leaves the payload contract and the failure mode on revision conflict unaddressed. Adequate to invoke, not sufficient to invoke confidently with a complex body.

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 0%, so the description must carry parameter meaning, and it only explains one of three required parameters: revision (0 for create, current for update). The `id` and the deeply nested `value` object (name, subject, previewText, body, serviceBlocks with service/divider/spacer variants) are entirely undocumented in both schema and description. Explaining the concurrency parameter well earns partial credit but does not compensate for the nested payload gap.

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 verb and resource ('Save an email campaign draft') and adds scope ('for review in Cockatoo'), which separates it from siblings like get_email_campaign_draft and save_welcome_email_draft. It stops short of explicitly contrasting with the closest alternatives (prepare_email_campaign_review, save_welcome_email_draft), so it is clear but not sibling-differentiating.

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 concrete conditional guidance for the create-vs-update decision: 'Use revision 0 for a new draft or the current revision to update it.' That is real when-to-use instruction rather than implied usage. It offers no exclusions or pointers to alternative tools for other draft types or for the review step.

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