Digital Maker AI

preview_podcast_studio

Create the studio picture for an Animated Podcast: two cartoon hosts at a podcast desk, one on each side, which is held on screen while they talk. Show it to the user and let them confirm or ask for another before calling create_podcast with its image_url. The user designs their own hosts: name, woman or man, and a description of how each looks, or a link to a photo to turn into the cartoon host. The set comes from the topic and setting, a ready-made room (list_podcast_studios shows them) or a link to their own empty-room picture. Images pasted straight into the chat cannot reach this tool; ask for a public link instead. If the user already has a finished studio picture, skip this and pass its link to create_podcast as studio_image_url. Spends no video minutes. Limited to a handful of new pictures per hour. Premium and Ultimate.

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": {
      "topic": "<topic>"
    },
    "name": "preview_podcast_studio"
  }
}

Input Schema

Name	Required	Description
`room`	No	Optional: the room the hosts are placed into. Either the name of a ready-made room from list_podcast_studios, or a public link (https) to the user's own picture of an empty room. Leave out to have the AI design the whole set from topic and setting.
`topic`	Yes	What the podcast is about, so the set fits it.
`host_a`	No	Left host.
`host_b`	No	Right host.
`setting`	No	Optional: the room or set in plain words, e.g. 'a cosy book-lined study' or 'a neon gaming den'.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 3, 2026

changedInput schema / properties / host_a / properties / photo_url / description

Previous value: -"Optional: a public link (https) to a photo of a person, redrawn as this cartoon host. Only a photo of the user themselves or someone who agreed to it."New value: +"Optional: a public link (https) to a photo of a person, recreated as this cartoon host. Only a photo of the user themselves or someone who agreed to it."

changedInput schema / properties / room / description

Previous value: -"Optional: the room the hosts are drawn into. Either the name of a ready-made room from list_podcast_studios, or a public link (https) to the user's own picture of an empty room. Leave out to have the AI design the whole set from topic and setting."New value: +"Optional: the room the hosts are placed into. Either the name of a ready-made room from list_podcast_studios, or a public link (https) to the user's own picture of an empty room. Leave out to have the AI design the whole set from topic and setting."

First observedOct 17, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does well: it states cost ('Spends no video minutes'), a rate limit ('a handful of new pictures per hour'), plan gating ('Premium and Ultimate'), a technical constraint (pasted chat images cannot reach the tool; need a public link), and a consent rule for photo_url. It does not explain iteration limits or whether regenerating counts against the same quota.

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 what the artifact is, then the confirm-then-create workflow, then input rules, then constraints. Dense and mostly waste-free, though the host-design and set-description sentences overlap somewhat with what the schema already documents.

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?

No output schema exists, and the description implies the return is a picture with an image_url referenced later by create_podcast, but never states the return shape explicitly (URL vs. displayed image, whether it persists). Otherwise complete for a nested, 5-parameter generation tool with zero annotations.

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 adds real meaning on top by explaining how inputs combine (hosts are self-designed via name/gender/look or photo link; the set derives from topic + setting, a ready-made room, or a user empty-room link) and the default behavior when room/setting are omitted. It also disambiguates image inputs (only public https links work).

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?

Opens with a specific verb and artifact: 'Create the studio picture for an Animated Podcast,' then describes the composition (two cartoon hosts at a desk, one each side, held on screen while they talk). This clearly separates it from create_podcast (which consumes the result) and list_podcast_studios (which supplies rooms).

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 when-to-use: generate a preview, show it, let the user confirm or request another, only then call create_podcast with its image_url. Explicit when-not-to-use: 'If the user already has a finished studio picture, skip this and pass its link to create_podcast as studio_image_url.' Alternatives (list_podcast_studios, user's own room link) are named with their conditions.

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

All Digital Maker AI 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?