Skip to main content
Glama

Create a public campaign pack

create_campaign_pack
Destructive

Create or open a public Superdraft workspace for a business website, requesting two email drafts and two Instagram posts with images designed as part of those drafts. Anyone with the workspace link can view and edit the saved content. Uses the shared public generation allowance and may resume failed setup. Returns promptly while generation continues. No standalone image generation, freeform image prompts, email sending, social publishing, or private account access.

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": "create_campaign_pack"
  }
}

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.3/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, openWorldHint=true and idempotentHint=false, and the description adds real context beyond them: the workspace is publicly viewable and editable by anyone with the link, it draws on a shared public generation allowance, and setup may resume after failure. The one gap is the mild tension with idempotentHint=false implied by 'create or open' and 'may resume failed setup' — it isn't explained whether a second call reopens the same workspace or starts a new one.

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?

Content is front-loaded: what is created comes first, visibility and billing semantics next, then the exclusion list. The middle sentences are dense and slightly run-on, but every sentence carries distinct information and none is padding.

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 single-parameter mutation tool with no output schema, the definition covers creation scope, public visibility, allowance consumption, resumability, and the asynchronous return. What it omits is how the agent should retrieve results afterward, which is left entirely implicit despite a get_campaign_status sibling existing.

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

Parameters4/5

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

Only one parameter exists and the schema describes it at 100% coverage, including the useful note that it accepts 'the canonical website_url returned by Superdraft'. The description adds only the framing that this is a public business website, which is marginal but consistent with the schema rather than redundant filler.

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 description states a concrete verb+resource ('Create or open a public Superdraft workspace for a business website') and enumerates exactly what is produced: two email drafts and two Instagram posts with images embedded in those drafts. This is clearly distinguishable from the read-oriented siblings get_campaign_pack and get_campaign_status 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 negative scope is explicit and useful: 'No standalone image generation, freeform image prompts, email sending, social publishing, or private account access' tells the agent what requests to route elsewhere. It also signals the async pattern ('Returns promptly while generation continues'), though it never names get_campaign_status as the follow-up for polling, leaving the agent to infer the completion path.

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