Riddle

riddle_builder_poll

Builds a Poll from a build configuration. For full block options see: https://www.riddle.com/help/api/build-riddles/riddle-types-and-other-blocks/poll. 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 Poll 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/5.0

Behavior3/5

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

The description is stronger than merely implying a mutation: it states 'Builds a Poll' and precisely describes the return envelope, including the conditional 'queued': true addition when queue is set. It does not mention publish behavior, persistent resource side effects, or the fact that unknown keys are rejected, and the only annotation (idempotentHint=false) leaves most behavioral disclosure to the description. The description covers the most important side effects but not the deeper creation semantics that an agent might need.

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 only three sentences: the core action, a direct reference to official documentation for full block options, and the response envelope guarantee. Every sentence earns its place, and the most important distinction is front-loaded. No filler or duplication of schema information is present.

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?

Given the complexity of nested build objects and six parameters, the description supplies the crucial high-level return format and links to the authoritative docs. The lack of an output schema puts some burden on the 'Returns the compact build-configuration envelope of riddle_get' clause, which it satisfies. The description leaves unwritten several behavioral checks and cross-tool workflows (validate before build, update after get, template lineage), but these are largely covered by the rich 100%-coverage schema and are not critical gaps.

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 every parameter is already documented in the input schema. The top-level description adds no per-parameter information beyond tying 'queue' to the response flag and framing 'build' as the raw build configuration. This meets the baseline where the schema performs the semantic heavy lifting and the description does not need to repeat it.

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 opens with 'Builds a Poll from a build configuration', which clearly states the tool's verb, resource, and operating context. It distinguishes this from the many sibling riddle_builder_* tools by naming the Poll type explicitly. The reference to the compact riddle_get envelope also clarifies exactly what kind of output the tool stages.

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?

'Builds a Poll' clearly identifies the correct general scenario for using the tool, and the sibling builder tools (quiz, story, minigame, etc.) make the differentiation obvious by name. However, the description does not explicitly explain when to prefer this over riddle_builder_update, riddle_builder_validate, or riddleTemplate_use, or when a user should send a templateId. There is no misleading guidance, but a stronger 'use this instead of X when you have a Poll build config' statement would be better.

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

All Riddle 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 has a clear, unique purpose. The riddle_builder_* variants are distinct by Riddle type, questionBank_* and riddleTemplate_* cover separate objects, and stats_* differ by scope. No two tools appear to perform the same function.

Naming Consistency4/5

Naming is largely consistent with domain prefixes (riddle_, questionBank_, riddleTemplate_, stats_, project_, palette_, reference_). Minor deviations like riddle_account_list vs. riddle_list and whoami (no prefix) and riddle_get_embed_code vs. riddle_qr_code slightly break the pattern, but overall it is predictable.

Tool Count2/5

With 62 tools, the server is far beyond the typical 3-15 well-scoped range. While each tool is functional and the breadth reflects the platform's complexity, the sheer number makes it heavy and increases the cognitive load for an agent, suggesting over-granularity.

Completeness5/5

The tool set covers the full lifecycle: create (builder variants), read (get/list), update (builder_update, rename), delete, publish/unpublish, tagging, templates, question banks, stats, projects, palettes, and reference documentation. No obvious domain operation is missing.

Resources

Need Help?