Skip to main content
Glama

Preview a step

preview_campaign_step
Read-only

Use this when the user wants to see what a step would actually say. Writes the step for the first person on the campaign's lists, as they would receive it, and returns it with that person. Nothing is saved or sent. A campaign with nobody to write for is refused. It can take a minute. Free.

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": {
      "campaignId": "<campaignId>",
      "stepId": "<stepId>"
    },
    "name": "preview_campaign_step"
  }
}

Input Schema

NameRequiredDescriptionDefault
stepIdYesThe step's id, as the campaign's steps list gives it.
campaignIdYesThe campaign's id.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.5/5.0
Behavior5/5

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

Beyond readOnlyHint/destructiveHint, it discloses the exact rendering behavior (written for the first person on the campaign's lists, returned alongside that recipient), confirms no persistence or delivery, documents the empty-recipient failure mode, and warns about latency and cost. That is precisely the extra context annotations cannot carry.

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?

Five short sentences, each carrying distinct information in a sensible order: trigger, mechanism, safety, failure, latency, cost. No repetition of the title or annotations, and the fragments ('It can take a minute. Free.') are deliberate and information-dense.

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?

For a two-required-id read tool with full schema coverage and annotations, the description covers intent, safety, output shape ('returns it with that person'), failure conditions, and performance/cost expectations. No output schema exists, but the return is described enough for an agent to use the result correctly.

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%, so both ids are already documented in the schema. The description only implicitly references them via 'the campaign's lists' and 'the step', adding no format, sourcing, or constraint detail beyond the schema. Baseline 3 is appropriate.

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?

The definition gives a specific verb and resource ('preview' / 'writes the step ... and returns it with that person') and frames it around the user's actual intent ('see what a step would actually say'). The line 'Nothing is saved or sent' clearly separates it from the mutation siblings such as update_campaign_step and add_campaign_step without needing their schemas.

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?

The opening sentence states an explicit trigger condition: use it when the user wants to see what a step would say. It also implies the when-not by clarifying nothing is persisted, so an agent won't confuse it with an edit. It stops short of naming a concrete alternative (e.g., get_campaign or list_campaign_steps) for the read-only-metadata case.

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