Skip to main content
Glama

Plunder & Riffle Meme Engine

Retro infomercial of a pitch's memes

create_infomercial

The memes of a FINISHED create_before_pitch as a ~30 second 1980s retro infomercial preview: each meme on an old TV, a billboard or a drive-in screen, then in close-up with retro actors (nothing new is generated). Async: poll get_job_status kind infomercial. Done carries pageUrl: show the human; only after they approve call request_mp4 with it. No credits for the preview.

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": {
      "job_id": "<job_id>"
    },
    "name": "create_infomercial"
  }
}

Input Schema

NameRequiredDescriptionDefault
muteNoNo voices.
seedNoAnother take: other memes and sets.
job_idYesThe jobId of a done create_before_pitch (pack_…).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

The only annotation is destructiveHint=false, so the description carries nearly the whole behavioral load and does so: async execution, the exact polling parameter value (kind infomercial), the output field (pageUrl on done), and a human-approval gate before spending anything. The 'no credits for the preview' note is real cost context an agent cannot get from structured fields.

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?

Front-loads the result first and then the workflow, so the most important information lands immediately. It is dense and packs async handling, approval gating, and cost into a few clauses, which slightly compresses readability but wastes no sentences.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter async generation tool with no output schema, it supplies everything an agent needs: how to poll, what field indicates success, that pageUrl must be surfaced to the human, and which follow-up tool to call after approval. Nothing essential about invocation or the downstream handoff is missing.

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?

Schema coverage is 100%, so the baseline is 3; the description earns a bump by reinforcing that job_id must reference a completed create_before_pitch and by framing the whole call as a preview-only variant. It does not add syntax or format detail beyond the schema for seed or mute, so it stops short of 5.

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 concrete verb and artifact: the memes of a FINISHED create_before_pitch rendered as a ~30 second 1980s retro infomercial preview, with a clear visual treatment (old TV, billboard, drive-in, then close-up with retro actors). The prerequisite input (a done create_before_pitch job) scopes it away from siblings like create_ridiculous or create_best_of.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Gives the full operating sequence: call it, poll get_job_status with kind infomercial, show the pageUrl to the human, and only call request_mp4 after approval. It also sets an exclusion ('nothing new is generated') and notes the preview costs no credits, so the agent knows exactly when this tool applies and when the downstream step is required.

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