Skip to main content
Glama

Preview campaign

campaign_preview
Read-onlyIdempotent

Renders a draft and returns the text version, the live audience_count, quota_after_send and warnings (empty subject, missing button, over quota, first campaign pending review). Free, read only, sends nothing. Always call this before campaign_schedule and tell the person the audience count, the quota it will use and every warning. Requires API key scope: draft.

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": "campaign_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesCampaign id (a UUID), as returned by campaign_draft or campaigns_list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so 'free, read only, sends nothing' mostly restates them. However, the description adds genuinely new behavior: the required API key scope ('draft'), that quota_after_send is computed live, and an enumerated list of warning conditions, which the agent needs to interpret output.

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 tight sentences: what it returns first, cost/safety second, required workflow and auth third. No filler, and the return payload is front-loaded where an agent will scan for it.

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?

There is no output schema, and the description compensates by naming every returned field and every warning type. Combined with the stated auth scope and sequencing requirement, an agent has everything needed to call it and act on the result.

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 `id` parameter is fully documented in the schema, including its UUID pattern and provenance. The description adds no further parameter meaning, 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?

States a specific verb (renders) and resource (a draft), then names the exact return payload: text version, live audience_count, quota_after_send, and warnings. An agent can distinguish it from campaign_draft (creates) and campaign_schedule (sends) without opening any 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?

Gives an explicit mandatory ordering rule ('Always call this before campaign_schedule') plus a downstream obligation ('tell the person the audience count, the quota it will use and every warning'). This is a clear when-to-use instruction tied to a named sibling.

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