Skip to main content
Glama

Campaign preview: the email's HTML. To see a campaign, use readCampaign

previewCampaign
Read-onlyIdempotent

For Kooga's views only, of no use to call otherwise. Campaign preview: the email's HTML. To see a campaign, use readCampaign.

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": {
      "broadcastId": "<broadcastId>"
    },
    "name": "previewCampaign"
  }
}

Input Schema

NameRequiredDescriptionDefault
variantNo
broadcastIdYes
workspaceIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive behavior, and closed-world scope. The description adds that the return is the email's HTML and that the tool is intended for internal viewing only, but it does not explain permissions, rate limits, or how the preview is generated.

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

Conciseness3/5

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

The description is short and contains only three sentence fragments, but the first fragment is awkward and partially redundant with the title. The purpose appears after the access restriction rather than being front-loaded.

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

Completeness2/5

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

For a tool with three undocumented parameters and no output schema, the description needs to resolve more than the broad purpose. It does not explain what broadcastId, workspaceId, or variant select, nor does it clarify what 'Kooga's views only' means in practice.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% with three parameters, and the description does not mention broadcastId, workspaceId, or the a/b variant enum at all. It only implies that some campaign identifier is involved, leaving the actual parameter meanings and constraints entirely undocumented.

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?

The description states that this tool previews a campaign's email HTML, which is a specific verb and resource, and it explicitly distinguishes the tool from readCampaign. The opening sentence about 'Kooga's views only' adds noise but does not obscure the core purpose.

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?

It explicitly says the tool is for Kooga's views only and is of no use to call otherwise, and it names readCampaign as the alternative for seeing a campaign. The guidance is clear, though the phrase 'Kooga's views only' is not defined.

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