Riddle Quiz Maker

riddle_builder_placeholder

Builds a Placeholder from a build configuration: a Riddle with no content of its own, only a routing rule that is resolved when the Placeholder is displayed, to decide which OTHER Riddle (or a Riddle picked by tag) to actually show. Requires the Placeholder feature, which has to be enabled for your account. The rule is never resolved through this API - riddleId and conditions are stored as-is and read back unevaluated, by riddle_get too. See the "conditions" build field for the important note on why what you send is not necessarily what you get back. Returns the compact build-configuration envelope of riddle_get (riddle://reference/response-format), with 'queued': true added when queue is set.

Input Schema

TableJSON Schema

Name	Required	Description
`omit`	No	Leaves parts of the returned envelope out. Values: "build", "warnings", "nextBlockId", "published", "context" (whole sections) and "build.omittedDefaults" (the per-block maps of properties left at their default, inside every build config in the response). Omit for the whole envelope. "uuid"/"type"/"modifiedAt" are always returned. Reach for omit: ["build.omittedDefaults"] on almost every build - it drops ~85-90% of the read-back and loses nothing, since riddle://reference/block-defaults/<block type> states the same defaults; what you must not do either way is resend those values. When you leave anything out the response names it under "omittedFields", so a missing key never means the Riddle has none of it. Same parameter as riddle_get's.
`build`	Yes	The Placeholder build configuration.This is the raw build configuration in the engine's own key names - the exact same shape riddle_get returns under "build", riddle_builder_update takes, and riddle_builder_validate dry-runs, so a read-back can be fed straight back in. Unknown keys are rejected rather than ignored.
`queue`	No	Whether to queue the creation asynchronously.
`project`	No	The project ID; pass NULL for personal project; omit to use the currently selected project.
`publish`	No	Whether to publish the Riddle right after creation; default is false (draft). Distinct from the "publish" field INSIDE the build config, which is the stored publish configuration object.
`templateId`	No	Only when this build config came from a template you adapted (riddleTemplate_get): the id of that template. Always pass it when you have one: it gives the new Riddle the template's DESIGN in full - its layout, palettes and every preset setting, including the parts no build config can express - with your build config applied on top of it, and it records the new Riddle as a copy of the template's Riddle, the same lineage riddleTemplate_use produces (riddle_get reports it as context.duplicated). The content is entirely yours either way. Omit it for anything you did not build from a template.

TDQS

A4.6/5.0

Behavior5/5

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

With only idempotentHint=false in the annotations, the description carries the behavioral burden and does so well: the rule is never resolved through this API, riddleId and conditions are stored as-is and read back unevaluated by riddle_get, the read-back may differ from what was sent, and the response gets 'queued': true when queue is set. This is the kind of non-obvious behavior the annotations do not provide.

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, front-loaded with the core purpose, and every sentence earns its place: the Placeholder definition, the feature requirement, the unevaluated routing rule, and the return envelope. It does not waste words restating the long schema.

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?

For a complex builder with no output schema, the description gives the essential response shape: the compact build-configuration envelope of riddle_get plus 'queued': true when queue is active. It relies on a riddle:// reference and on riddle_get for the exact envelope details, which is reasonable but slightly indirect.

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?

There is 100% schema description coverage, so the schema already explains each parameter. The description still adds value by warning that conditions/riddleId are stored literally and unevaluated, pointing to the critical conditions note, and explaining when the queued flag appears in the response. That is above the baseline but the exact parameter shapes still live in the 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?

The description names a specific verb and resource ('Builds a Placeholder') and immediately distinguishes it from the other riddle_builder_* siblings: this kind of Riddle has no content of its own, only a routing rule. It is not a tautology and leaves no doubt about the object being created.

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 clearly establishes when this builder is relevant: when a routing-only Riddle is needed that resolves to another Riddle or a tag. It also adds the feature-requirement precondition. It stops short of a 5 because it does not explicitly name sibling tools as alternatives or say 'use a different builder when you actually need content'.

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

All Riddle Quiz Maker tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation4/5

Tools are largely distinct by name and detailed descriptions, with clear prefixes (riddle_builder_*, questionBank_*, stats_*). Some potential confusion exists among the stats tools (stats_fetch vs stats_overview_fetch vs breakdowns) but descriptions clarify their different scopes. Overall, an agent can usually pick the right tool.

Naming Consistency4/5

Naming follows a predictable prefix+verb pattern within each domain (e.g., riddle_builder_quiz, riddle_builder_poll; riddle_get, riddle_publish). Minor inconsistencies exist, like the camelCase 'questionBank' and 'riddleTemplate' prefixes vs snake_case elsewhere, and 'stats_overview_fetch' ordering, but these are not chaotic and remain readable.

Tool Count1/5

With 62 tools, this far exceeds the recommended 3-15 range and even the 25+ threshold. While the server covers a broad domain, the extreme number overwhelms and makes tool selection harder, fitting the 'extreme mismatch' criterion for 50+ tools.

Completeness5/5

The tool surface is exceptionally comprehensive, covering creation, reading, updating, deleting, publishing, unpublishing, moving, tagging, template management, question banks, palettes, and various stats breakdowns. There are no obvious gaps in the lifecycle of managing interactive content, and all apparent operations are supported.

Resources

Need Help?