Skip to main content
Glama

Plunder & Riffle Meme Engine

Product ad copy and creatives

shop

The /shop push pack: any product link or description → researched, ready-to-post copy (hooks, meme lines, iMessage thread, CTA, hashtags, first comment) plus up to 3 creatives (TEMP PAGE previews + PNGs + post_copy). 10 credits for the context + each format's list credits; BYOK: $0.01. Each part refunded on its own failure. ~30–90s.

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": {
      "input": "<input>"
    },
    "name": "shop"
  }
}

Input Schema

NameRequiredDescriptionDefault
refNoYour referral code (returned in referralUrl).
brandNoBrand key (default house brand).
inputYesA product/page link, or a description of the product when there is no link (≤1500 chars).
sizesNoPNG sizes (default all). Not the creative `format`.
languageNoDefault English.
allFramesNoExport every slide (max 10). Default true for carousel/hybrid.
creativesNoCreative formats to build (max 3); omitted = one single meme, [] = copy only. iMessage / text thread → "hybrid"; carousel / slideshow → "carousel"; hot take → "hottake"; confession → "confession"; single meme / image → "image".
directionNoOptional angle/audience/tone, e.g. "for burnt-out PMs".
brandProfileNoAd-hoc brand voice, overrides `brand`: name, voice (≤1000), hashtag, token, ctaStyle {tone, action (no URL), linkPlacement first-comment|caption, avoid[], examples[]}.
includeAssetsNoRender PNGs and return URLs (default true; false for single memes).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With only destructiveHint=false supplied, the description carries the burden well: it discloses the credit cost model (10 credits for context plus per-format list credits), the BYOK rate ($0.01), per-part refunds on partial failure, and an expected runtime of ~30–90s. Gaps remain on auth/permission needs and on what a 'TEMP PAGE' preview actually is or how long it persists.

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?

It is front-loaded with the transformation and the deliverables before cost and timing, and uses compact arrow notation to avoid filler. It leans on internal jargon ('/shop push pack', 'BYOK', 'TEMP PAGE') that slightly reduces first-read clarity, but no sentence is wasted.

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 10-parameter, nested-object tool with no output schema, the description still enumerates the return artifacts (copy components, preview page, PNGs, post_copy) and covers cost, latency, and partial-failure semantics. What is missing is the no-link vs link branching behavior and error/credit-insufficiency handling, which an agent would want before invoking.

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 100% and each parameter including the nested brandProfile is already documented, so the baseline is 3. The description only reinforces two facts already in the schema (max 3 creatives, iMessage→hybrid mapping is schema-side), adding no new syntax, format, or precedence detail beyond the credit-cost interaction between context and formats.

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 transformation (product link or description → researched copy plus up to 3 creatives) and enumerates the deliverables (hooks, meme lines, iMessage thread, CTA, hashtags, first comment, PNGs, post_copy). It is far more specific than the title alone, but it never distinguishes itself from likely siblings such as generate_ad_creative or create_best_of, so an agent must infer the boundary itself.

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 only implied through the input shape ('any product link or description'), which does suggest when this tool fits. There is no explicit when-not guidance, no mention of prerequisites (brand setup, credits balance checks), and no naming of alternatives for narrower jobs like a single ad creative.

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