Skip to main content
Glama

Build campaign pack

build_campaign_pack

One zip for go-live: each platform's image (exact size, overlay and small print baked in) and edited video, with covers, caption files and a README, all named for the platform, plus checks for anything a platform would reject. No Higgsfield credits used. Use dry_run first.

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": {
      "platforms": "<platforms>"
    },
    "name": "build_campaign_pack"
  }
}

Input Schema

NameRequiredDescriptionDefault
ctaNo
brandNoThe full brand, only when there is no kit for it. brand_id is simpler.
videosNoFinished render_video renders: their measured loudness, cover and caption files come with them
dry_runNoCheck and plan the pack without building it
overlayNo
staticsNo
brand_idNoA brand kit from list_brands (id or name). Brings the colours, fonts, logo, website and default copy (headline, call to action, small print); use instead of brand.
headlineNo
platformsYesreels: Instagram Reels; tiktok: TikTok; shorts: YouTube Shorts; ig-feed: Instagram feed; fb-feed: Facebook feed; linkedin: LinkedIn; x: X; pinterest: Pinterest
small_printNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=false) the description adds two meaningful traits: it runs local validation checks for 'anything a platform would reject' and it uses no Higgsfield credits, which is cost information an agent cannot get from structured fields. It stops short of saying what happens if the zip already exists or whether the operation is repeatable.

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?

Two sentences, front-loaded with the concrete deliverable and followed by the cost note and the dry_run recommendation. The first sentence is dense but every clause names a real artifact in the pack; nothing reads as filler.

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?

With ten parameters, nested objects and no output schema, the description usefully enumerates what the returned zip contains, which partly substitutes for a missing output schema. It omits prerequisites (finished renders, an existing brand kit), what dry_run actually returns, and failure behavior for platforms that reject content, so it is adequate but not complete for a tool of this complexity.

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 50% across ten parameters with nested objects, so the description must carry some weight. It clarifies that sizes, overlay and small print are baked in and that content is named per platform, which maps loosely to the overlay, small_print and platforms params, plus the dry_run hint. It adds nothing about the brand vs brand_id distinction, videos vs statics, or the job_token and crop fields.

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 states a concrete output: a single zip containing per-platform sized images, edited video, covers, caption files and a README, all platform-named. That is specific enough to distinguish it from asset-creation siblings like compose_asset or add_graphic, though it never names those alternatives explicitly.

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?

Usage is implied by 'for go-live' and the instruction 'Use dry_run first', which gives a safe first step. There is no explicit statement of when to pick this over sibling tools such as clean_up_promo or compose_asset, and no stated prerequisites for calling it.

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