Skip to main content
Glama

Plunder & Riffle Meme Engine

Check a job

get_job_status
Read-only

Poll any async job by kind: mp4 (request_mp4), sitdown (create_best_of / create_ridiculous / create_news), scroll (create_before_scroll), infomercial (create_infomercial), before_text (create_before_pitch with feed or offer), funnel (create_funnel, jobId = funnelId). Free. Poll while terminal is false, every pollAfterSec. phase: working, done (mp4Url or pageUrl), failed (refunded) or needs_input (ask the human); status is the kind's own word. A done sitdown job carries followUp: pass its jobId to create_followup for another post from the same script.

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": {
      "kind": "<kind>",
      "jobId": "<jobId>"
    },
    "name": "get_job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
jobIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds real context beyond that: cost ("Free"), polling cadence, and the phase vocabulary including that failed jobs are refunded. It does not explain what `status` values look like per kind beyond "the kind's own word", nor error/timeout behavior for a job that never terminates, so it adds value but not full behavioral depth.

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 kind→creator mapping, then polling mechanics, then return semantics — a sensible information order with no filler. It is dense semicolon-chained prose that rewards a careful read but stays compact for the amount of routing and phase information it conveys.

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?

There is no output schema, and the description compensates by naming the return fields an agent must branch on (`phase`, `mp4Url`/`pageUrl`, `followUp`, `terminal`, `pollAfterSec`, `status`). Combined with the enum mapping, nothing needed to call or interpret a result 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 0%, so the description must carry the enum's meaning — and it does, enumerating the kind values and naming their producing tools, plus the special case `jobId = funnelId` for funnel. The general meaning of `jobId` (the id returned by the corresponding create_* call) is only implied rather than stated outright, which keeps this short of a 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 specific verb (poll) and resource (any async job) and immediately disambiguates scope by mapping each `kind` value to the sibling creation tool that produced it (mp4 → request_mp4, sitdown → create_best_of/create_ridiculous/create_news). An agent can tell exactly what this tool reads and which jobs it covers without opening a schema.

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 operating instructions: poll while `terminal` is false, at `pollAfterSec` intervals, and treat needs_input as "ask the human". It also routes onward — pass a done sitdown job's `followUp` jobId to create_followup — so both when-to-use and the next-tool handoff are stated rather than inferred.

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