Riddle

riddle_builder_personality

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

Behavior4/5

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

With only idempotentHint=false in the annotations, the description carries some important behavioral disclosure: 'Builds' signals a non-read-only creation operation, and it adds a useful response behavior detail by mentioning the compact riddle_get envelope and the conditional 'queued': true field. It does not state authentication or side effects beyond creation, but it does not contradict the annotation and adds value beyond it.

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 concise and front-loaded: the first sentence states the core purpose, and the second sentence explains the return shape and queue behavior. The external documentation link is a useful pointer, not filler, and no sentence restates schema content unnecessarily.

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?

Although this is a complex tool with nested parameters and no output schema, the description compensates by naming the return envelope and the queue edge case. The full input-schema descriptions cover parameter behavior, but the tool could be slightly more complete by explicitly saying when to choose this builder over the adjacent riddle_builder_* tools, so it falls just short of a 5.

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%, and every parameter, including the nested build object, already carries detailed descriptions. The free-text description adds little parameter-level meaning beyond the phrase 'build configuration,' so the baseline of 3 is appropriate; it does not deserve more credit for semantic redundancy with 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 opens with 'Builds a Personality Test from the build configuration,' naming a specific verb and a concrete resource type. This clearly distinguishes it from sibling builder types such as quiz, poll, and leaderboard because it names the exact riddle type it creates. The follow-up about the response envelope confirms this is a creation/builder operation rather than a read or update.

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 makes the intended use clear: use this tool to build a Personality Test from a build configuration. It does not explicitly spell out when not to use it or name alternative builders, but the sibling tool names and the distinct 'Personality Test' resource give an agent the context needed to select this tool correctly.

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?