agent-media

make_series_cover

Paid (1 image). Make a vertical 2:3 cover for your series from its cast: lead a and lead b close together in a romantic or tense pose that stays non-explicit, in the series' main location, with the title and logline as text. dry_run true (the default) returns its price in credits and makes nothing: show say and the price. After the customer's yes, call with dry_run false (same note): it makes one image and returns image_url, credits and say; calling again with the same values never pays twice, and a note (a short direction, 200 characters at most) makes a new take. The image is not the cover yet: show it, and after the customer's yes call with approve true (charges nothing) to set it as the cover, or use set_series_cover with image_url. Not made returns cover_made false with reason (cast_not_ready, price_unavailable, still_making: call again with the same values, image_refused, not_enough_credits, make_failed) and say (post it as is).

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": {
      "series_id": "<series_id>"
    },
    "name": "make_series_cover"
  }
}

Input Schema

Name	Required	Description	Default
`note`	No
`approve`	No
`dry_run`	No
`series_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true) by disclosing cost behavior ('Paid (1 image)', price returned in credits), idempotency ('calling again with the same values never pays twice'), that approve charges nothing, and the note length cap. It also enumerates the failure reasons and their handling (still_making means retry with same values; say must be posted as is).

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 cost and purpose, then sequences the workflow in call order, with zero filler sentences. It is dense to the point of being slightly run-on, packing multiple operations into semicolon-chained clauses, but every clause conveys a distinct operational fact.

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 paid, multi-stage, stateful generation tool with no output schema, the description covers pricing, confirmation gates, idempotency, approval path, and all documented failure codes with recovery instructions. An agent has everything needed to call it and interpret the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description carries the full burden and does: dry_run's default and its price-only behavior, approve's zero-charge cover-setting effect, and note as a short direction capped at 200 characters that produces a new take. This is meaning no agent could infer from the bare boolean/string schema.

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 ('Make a vertical 2:3 cover for your series from its cast') plus the composition, location and text overlays. It also distinguishes itself from the sibling set_series_cover by noting that the generated image is not yet the cover, routing the agent 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?

Gives an explicit staged workflow: dry_run true (default) to get a price, dry_run false only after the customer's yes, then approve true or set_series_cover with image_url. It names the alternative tool and the condition that selects it, and specifies 'same note' for retry and 'a note makes a new take'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All agent-media tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?