Skip to main content
Glama

List a campaign's steps

list_campaign_steps
Read-only

Use this when you need a campaign's steps in the order they run: each step's channel, type, wait, subject and message, and, in a branched sequence, the condition and lane a step sits under. 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>"
    },
    "name": "list_campaign_steps"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaignIdYesThe campaign's id.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint true, destructiveHint false, openWorldHint false), but the description adds two things they don't: the call is "Free" (a cost signal an agent can use for budgeting) and the exact payload shape, including branch-specific fields like condition and lane. It says nothing about behavior when a campaign has no steps or an invalid id, which leaves a small gap.

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?

A single front-loaded sentence opens with the usage trigger before the field enumeration, and every clause contributes information about the result shape. The trailing field list and the isolated "Free." fragment make it slightly run-on, but nothing is redundant.

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

Completeness4/5

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

For a one-parameter read tool with annotations and no output schema, the description is nearly self-sufficient because it enumerates the returned fields rather than deferring to a schema that doesn't exist. The only missing piece is edge-case behavior (empty campaigns, unknown ids), which is minor for a read-only list operation.

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 campaignId is documented with a format constraint (24-char hex pattern, min/max length), so the schema carries the parameter semantics. The description adds no format, sourcing, or lookup guidance beyond "a campaign's steps," making the baseline 3 appropriate.

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 names a specific verb and resource (list a campaign's steps) and enumerates the fields returned — channel, type, wait, subject, message, condition, lane — so the agent knows exactly what comes back. It never names a sibling such as list_campaign_queue or preview_campaign_step to sharpen the boundary, so differentiation is left implicit.

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?

"Use this when you need a campaign's steps in the order they run" gives a clear selecting condition, including the ordering semantics that matter for sequence inspection. It offers no exclusions or explicit alternatives, so an agent must infer that add_campaign_step and regenerate_campaign_steps are non-overlapping.

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