Skip to main content
Glama

Generate an editable campaign pack

generate_campaign_pack
Read-onlyIdempotent

Create three editable SVG assets (square, story, landscape) and a reusable field manifest from an offer, brand colors, dates and HTTPS destination. Fixed templates; no Canva connection, external images, account access, publication or storage.

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": {
      "businessName": "<businessName>",
      "offer": "<offer>",
      "startDate": "<startDate>",
      "endDate": "<endDate>",
      "cta": "<cta>",
      "destinationUrl": "<destinationUrl>",
      "brand": "<brand>"
    },
    "name": "generate_campaign_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
ctaYes
brandYes
offerYes
endDateYesISO calendar date (YYYY-MM-DD)
locationNo
startDateYesISO calendar date (YYYY-MM-DD)
disclaimerNo
isSyntheticNo
businessNameYes
destinationUrlYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, but the description adds real substance on top: fixed templates, no external image fetching, no account/auth requirement, and nothing persisted or published. It does not state the output file naming/format delivery mechanism, which keeps it from 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the deliverable, followed by the scope boundary. No filler, no restatement of the title, and the negative constraints are packed into a single readable clause.

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 does the necessary work of saying what is returned: three SVGs plus a reusable field manifest. It leaves the manifest's contents and the asset delivery format (paths? inline data? attachments?) unspecified, which matters for a 10-parameter generator, but the core completeness bar is met.

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 only 20% across 10 parameters, so the description carries extra burden; it names offer, brand colors, dates and HTTPS destination, which covers the most consequential inputs. It says nothing about cta, businessName, location, disclaimer, or isSynthetic, and adds no constraint detail (e.g. the 36-char CTA cap or why HTTPS is mandated) beyond what the schema already enforces.

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 specific verb (create) and enumerates the exact artifacts produced: three editable SVG assets in named formats (square, story, landscape) plus a reusable field manifest. The input basis is also named (offer, brand colors, dates, HTTPS destination), so an agent knows precisely what comes out 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 Guidelines3/5

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

The second sentence effectively defines when NOT to reach for this tool by ruling out Canva connection, external images, account access, publication and storage. However, there is no positive when-to-use framing or explicit alternative named (the only sibling, analyze_marketing_report, is an analysis tool and is never referenced), so guidance is implied rather than stated.

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