Manawa Terminal

Marketing render

marketing_render

Admin only. Render one live format and wait until image.url exists.

Blocks until GCS has the PNG (or a cache hit). Do not poll. Draft
formats return option_not_live.

Args:
    content_id: gc:{id} or rd:{uuid}
    option_id: live option from marketing_graphics
    force: Bypass render cache

Input Schema

TableJSON Schema

Name	Required	Description	Default
`force`	No
`option_id`	Yes
`content_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 21, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The description goes well beyond the annotations by disclosing blocking behavior ('Blocks until GCS has the PNG'), cache behavior ('or a cache hit'), the 'Do not poll' directive, the draft-format error condition, and the admin-only restriction. It also explains the force parameter's cache-bypass effect, giving the agent a clear model of the tool's runtime behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded, with the most important facts ('Admin only', 'Render one live format', blocking behavior) in the first sentence. The Args section is clearly formatted and each line adds distinct value with no redundancy or filler.

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?

Given the tool's moderate complexity, the description covers prerequisites (admin, live option), input format, blocking semantics, error behavior for drafts, and cache-related options. Since an output schema is present, return-value details are not required, and nothing essential for correct invocation is missing.

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 description coverage is 0%, so the description carries the full burden for parameter meaning. It fully compensates by explaining content_id format ('gc:{id} or rd:{uuid}'), option_id origin ('live option from marketing_graphics'), and force semantics ('Bypass render cache'), covering all three parameters with actionable detail.

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?

The description states a specific action: 'Render one live format and wait until image.url exists.' It clearly identifies the resource (live marketing format), the operation (render), and the async behavior, and it references the sibling tool 'marketing_graphics' as the source of valid option_ids, which helps distinguish this from related tools.

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

Usage Guidelines4/5

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

The description gives clear operational guidance: admin-only access, render live formats only, wait for the image URL rather than polling, and expect option_not_live for draft formats. It lacks an explicit 'when not to use this tool' or named alternative tools, but the draft-format exclusion and pointer to marketing_graphics provide strong contextual routing.

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

All Manawa Terminal 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?