Riddle Quiz Maker

riddle_builder_create

Builds a new Riddle of any of the nine types from a build configuration: "type" says which kind (see that argument for what each one is and what it needs at a minimum), "build" carries the content. Everything a type accepts is described on the "build" fields themselves, marked with the types it belongs to; the exhaustive per-type shapes are in riddle://reference/riddle-builder/riddle-types, the block types in riddle://reference/riddle-builder/block-types, and the human help pages at https://www.riddle.com/help/api/build-riddles/riddle-types-and-other-blocks/. To change an existing Riddle instead, use riddle_builder_update (a merge, not a rebuild); to check a configuration without creating anything, riddle_builder_validate. Returns the compact build-configuration envelope of riddle_get (riddle://reference/response-format), with 'queued': true added when queue is set. The new Riddle's view URL comes back in it - "context.viewUrl" once published, "context.viewUrlUnavailable.url" (already final, not live yet) before that.

Input Schema

TableJSON Schema

Name	Required	Description
`omit`	No	Sections of the returned envelope to leave out; omit the parameter for the whole envelope. "uuid"/"type"/"modifiedAt" are always returned, and whatever you leave out is echoed back under "omittedFields", so a missing key never means the Riddle has none of it. Details: riddle://reference/concepts/warnings.
`type`	Yes	Which kind of Riddle to build - this decides which "build" fields and which block types exist. Quiz: questions with right and wrong answers, scored, one result page per score range (title + blocks). Poll: opinion questions, nothing right or wrong, one shared result page (title + blocks). Personality: answers score towards personalities, the winner is the result (title + blocks + personalities). Form: lead-collecting fields only, no questions (title + blocks). Predictor: predictions of real-world outcomes, scored once the actual result is entered (title + blocks). Minigame: SlotMachine, WheelSpinner, Sudoku, Minesweeper or Crosswords (title + blocks). Story: linear content pages, no answers of any kind (title + blocks). Leaderboard: a standalone ranking other published Riddles connect to, no blocks (title). Placeholder: no content of its own, routes to another Riddle by prioritized, time-windowed rules (title). Per-type shapes: riddle://reference/riddle-builder/riddle-types.
`build`	Yes	The build configuration of the Riddle type named in "type".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 - riddle_get's "build" KEY, never the outer envelope around it, whose "uuid" and siblings are rejected as unsupported properties. Unknown keys are rejected rather than ignored. WHICH fields exist is decided by "type": each one below opens with the types it belongs to, and a field the chosen type does not have is rejected. Only "title" exists on all nine.
`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 false (draft). Distinct from the "publish" field INSIDE the build config, which is the stored publish configuration.
`templateId`	No	Only when this build config came from a template you adapted (riddle_template_get): that template's id. Always pass it when you have one - the new Riddle then starts out on the template's whole DESIGN, including what no build config can express, with your build config applied on top. The content is yours either way. Details: riddle://reference/concepts/unknown-properties.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

AddedSep 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations are minimal and the description adds useful behavioral context: a new Riddle is persisted, queueing is possible ('queued': true), and the returned view URL has distinct pre/post-publication states. It does not exhaustively cover failure modes or permissions, but it meaningfully supplements the annotations without contradicting them.

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 long, but every sentence earns its place: purpose, sibling differentiation, return contract, and references are all packed in without redundancy. It is appropriately dense for a tool with this much configuration surface.

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, yet the description explains the returned envelope and the view URL behavior. It also points to exhaustive references for riddle types, block types, and response format, covering the tool's complexity well enough for an agent to use it correctly.

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

Parameters3/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds useful top-level orientation by explaining that 'type' selects the kind and 'build' carries the content, but it does not add substantial per-parameter meaning beyond what the schema already provides.

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 the exact action with a specific verb and resource: 'Builds a new Riddle.' It also names the differentiating siblings, riddle_builder_update and riddle_builder_validate, so there is no confusion about this being the create tool among the sibling Riddle tools.

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?

It gives explicit routing guidance: use riddle_builder_update to change an existing Riddle, and riddle_builder_validate to check a configuration without creating. This clearly tells an agent when to choose this create tool versus the alternatives.

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

A4.1/5.0

Disambiguation5/5

Each tool targets a distinct resource and action: media, palettes, projects, question banks, Riddle builds, publish lifecycle, tags, and templates are cleanly separated. Even near-neighbors like question_bank_get versus question_bank_get_items or riddle_tag versus question_bank_tag are disambiguated by explicit scope descriptions.

Naming Consistency4/5

Names follow a consistent lowercase snake_case domain-prefix plus action pattern, such as riddle_get, riddle_publish, question_bank_create, and media_delete. Minor deviations like question_bank_item, question_bank_manage, and the standalone ping/whoami break the pattern slightly.

Tool Count2/5

At 38 tools, the set is well above the 25+ threshold and is heavy for an agent to navigate in a single context. Most tools are individually justified, but the surface could be consolidated, particularly around tag operations, template listing variants, and question bank actions.

Completeness4/5

The Riddle lifecycle is well covered: build, validate, update, publish, unpublish, move, rename, delete, embed, tag, and fetch stats. Minor gaps remain, such as no template delete/update, no media library listing, and no project create/update/delete, but these are workable around or arguably outside the core domain.

Resources

Need Help?