Skip to main content
Glama

Check a public campaign pack

get_campaign_status
Read-onlyIdempotent

Read the saved public campaign status for a business website. Returns queued, running, ready, partial, or failed and the workspace link. Does not start or retry generation. Use the canonical website_url returned by create_campaign_pack when available.

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": {
      "website_url": "<website_url>"
    },
    "name": "get_campaign_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
website_urlYesThe public business website or the canonical website_url returned by Superdraft.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely useful behavior: it is a snapshot read ('saved'), returns one of five enumerated states plus a workspace link, and has no side effects on generation. It says nothing about staleness or polling frequency.

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 short sentences, front-loaded with purpose, then return shape, then exclusions and parameter sourcing. No redundant phrasing.

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?

A read-only single-parameter tool with no output schema; the description compensates by enumerating return states and the workspace link. Minor gaps remain around unknown-URL failure behavior and refresh semantics.

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 parameter's description already explains the website or canonical URL. The description only lightly reinforces the canonical-URL guidance, so baseline 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 precise verb ('Read') and resource ('the saved public campaign status for a business website'), enumerates the possible status values, and clarifies scope by declaring it does not start or retry generation, which separates it from create_campaign_pack.

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?

Gives an explicit exclusion ('Does not start or retry generation') and tells the agent which URL to pass and where it comes from ('the canonical website_url returned by create_campaign_pack when available'). It stops short of saying when to prefer get_campaign_pack over this tool, so 4 rather than 5.

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