Skip to main content
Glama

Read a public campaign pack

get_campaign_pack
Read-onlyIdempotent

Read available public starter email subjects, preview text, bodies, Instagram captions, image links, and draft links for a business website. Includes slot states so missing drafts are not mistaken for finished work. Reads only public content; does not generate, edit, send, publish, or access private accounts.

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

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower, yet the description still adds real value: it explains that slot states are included so missing drafts are not mistaken for finished work, and that only public content is reachable with no private-account access. It does not mention pagination, response size, or failure behavior for a site with no pack, which keeps it below a 5.

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?

Three sentences, front-loaded with the returned content types, then the slot-state caveat, then the scope limits. Efficient overall, though "public" and "read" are restated in both the first and third sentences, costing a little redundancy.

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?

With no output schema, the description carries the return-value burden and does list the field families plus the slot-state concept, which is the key thing an agent needs to interpret missing data. It does not describe the response structure or how slot states are labeled, leaving a small gap for a read-only tool with no output schema.

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% for the single parameter, and the schema already explains that it accepts a public business website or the canonical website_url from Superdraft. The description only echoes "for a business website" and adds no format, normalization, or fallback guidance beyond the schema, so the 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?

The description opens with a specific verb and resource ("Read available public starter email subjects, preview text, bodies, Instagram captions, image links, and draft links") and enumerates exactly what content is returned. The closing clause "does not generate, edit, send, publish" implicitly separates it from the create sibling, so an agent can tell a read from a generation call without opening the schema.

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?

It gives a clear context for use — fetching already-prepared public starter content for a website — and states what it will not do (generate, edit, send, publish, access private accounts). It stops short of naming the alternative tool to call when content does not yet exist (create_campaign_pack), leaving that routing to inference.

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