Skip to main content
Glama

List campaigns

spur_list_campaigns
Read-onlyIdempotent

The user's campaigns (bulk email, SMS, direct mail, outreach) with status and recipient progress.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "spur_list_campaigns"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum campaigns to return
offsetNoCampaigns to skip, for paging
statusNoOnly campaigns with this status

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / status / enum
      Previous value: -[
      -  "draft",
      -  "active",
      -  "paused",
      -  "completed",
      -  "cancelled"
      -]New value: +[
      +  "draft",
      +  "active",
      +  "paused",
      +  "completed",
      +  "cancelled",
      +  "failed"
      +]
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description contributes the return content (status and recipient progress), which is useful since there is no output schema, but it says nothing about result ordering, pagination behavior, or whether all campaigns or only recent ones are returned.

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 short sentence-fragment with zero filler, but it is under-specified rather than efficient: there is no lead statement of the action and little front-loaded framing for the agent.

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 simple, non-destructive list tool with full schema coverage and rich annotations, the definition is close to adequate. Gaps remain around pagination expectations and the scope of results (the user's own campaigns only), which the description does gesture at but does not clarify.

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 limit, offset and the status enum are fully documented in the schema; baseline is 3. The description adds no meaning beyond that and its use of the word 'status' for a returned field could be confused with the status filter parameter.

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 the resource and qualifies it with the campaign channels covered (bulk email, SMS, direct mail, outreach) plus the fields returned (status, recipient progress), which is more than the name alone conveys. It lacks an explicit verb, but the noun phrase plus the sibling context of other list_* tools makes the intent unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this versus alternatives, no mention of when results should be paged, and no prerequisites or exclusions. The schema's limit/offset/status parameters imply filtering and paging, but the description itself gives no usage context.

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