Skip to main content
Glama

Plunder & Riffle Meme Engine

Scroll video of a pitch's examples

create_before_scroll

The five examples of a FINISHED create_before_pitch as a ~20 second vertical scroll video preview, with a minor track of Joe reacting like a friend going through them (no new examples are generated). look: feed (a For You scroll), phones (a row of phones) or chat (a group chat sending them around). Async: poll get_job_status kind scroll (seconds muted, about a minute with the track). Done carries pageUrl and joeSays: show the human; only after they approve call request_mp4 with the pageUrl. 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_before_scroll"
  }
}

Input Schema

NameRequiredDescriptionDefault
lookNoDefault: picked from the brand's seed.
muteNoNo Joe track.
seedNoAnother cut of the same five (same look + seed = same cut).
job_idYesThe jobId of a done create_before_pitch (pack_…).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only assert destructiveHint=false, so the description carries most of the burden and does it well: it discloses async behavior, the ~20 second muted render time with the track, that no credits are consumed for the preview, and the approval checkpoint before request_mp4. It does not describe failure modes or what happens if the source pitch is not finished.

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-loaded with the core purpose and structured around look, async flow, and approval gate, with essentially no filler. However the telegraphic sentence fragments ('Async: poll get_job_status kind scroll') and nested parentheticals make it denser than it needs to be for an agent to parse quickly.

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?

Despite having no output schema, the description tells the agent what a completed job returns (pageUrl and joeSays) and what to do with it. For a 4-parameter async preview tool with one required input, nothing an agent needs in order to invoke and follow up correctly 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 prose adds real meaning on top by explaining what each look actually renders (a For You scroll, a row of phones, a group chat) and by clarifying that seed yields another cut of the same five and mute removes the Joe track. The interaction between look seeds and defaults is only lightly covered.

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 and resource: turns the five examples of a FINISHED create_before_pitch into a ~20 second vertical scroll video preview. It also explicitly separates itself from create_before_pitch (the input must already be done) and from request_mp4 (the later step), so an agent can route correctly.

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?

Explicit sequencing: only call once create_before_pitch is finished, then poll get_job_status with kind scroll, show the human the pageUrl and joeSays, and call request_mp4 only after approval. It also names the exclusionary detail that no new examples are generated.

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