Skip to main content
Glama

riddle_unpublish

Unpublishes one or many Riddles; meaning each Riddle will no longer be available via https://www.riddle.com/view/[RIDDLEID]. A LIVE Leaderboard with active Riddle connections cannot be unpublished - use riddle_delete on it instead, which is always allowed and cleans up the connected Riddles automatically. Unpublishing a Riddle that is not live in the first place is not an error but a no-op, and it says so: the response carries a "message" stating that nothing was taken offline, either because the Riddle was never published (its content is then not checked for conflicts at all - that refusal only applies while a Riddle is live) or because it was already offline. Read that "message" before reporting a Riddle as "taken offline"; "context.published.at" is null in all of these cases and cannot tell them apart. Pass UUID for a single Riddle - the response is then the same compact build-configuration envelope riddle_get returns, with the cleared published state under "context.published"; use "omit" to shrink it the same way as riddle_get. Pass UUIDs (array of Riddle UUID strings, max 100) to unpublish several at once; the response is then the bulk envelope {bulk: true, operation, summary, results: [...]} with the new state per Riddle. A bulk unpublish is not atomic and never gives up early: a Riddle that cannot be unpublished (e.g. a Leaderboard with active connections) is reported as that entry's "error" while all other Riddles are still unpublished. A refusal says which content stands in the way: it fails with error "RIDDLE_UNPUBLISH" and a "validationErrors" list of {message, code, ...} entries - the same two-list failure shape riddle_publish uses, see riddle://reference/response-format ("errors").

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
UUIDNoThe UUID of the single Riddle you want to unpublish. Pass either this or UUIDs.
omitNoSame "omit" parameter as riddle_get's, applied to the single-UUID response envelope (see riddle_get for the full description). Has no effect on the bulk (UUIDs) response, which never carries a build configuration to begin with.
UUIDsNoSeveral Riddles to unpublish at once, as Riddle UUID strings, e.g. ["6FA740EW", "OllsevHa"] (max 100). Pass either this or UUID.

TDQS

A5/5.0
Behavior5/5

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

There is only idempotentHint=false as an annotation, so the description carries the burden of behavioral disclosure. It exposes no-op semantics, the null context.published.at caveat, non-atomic bulk behavior, refusal errors, and the bulk envelope. The no-op claim does not contradict idempotentHint=false, since the hint is not a positive claim of non-idempotency and the tool may still behave idempotently in these states.

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 covers a distinct operational rule: purpose, exception, no-op, single mode, bulk mode, failure behavior. It is front-loaded with the primary purpose and avoids repeating boilerplate. The density is appropriate for the tool's genuine complexity.

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?

With no output schema, the description must explain return values, and it does so comprehensively for single, bulk, and error cases. It even tells the agent how to interpret ambiguous responses and where to find complete error-standard documents. Nothing essential is missing to call and interpret the result of this tool correctly.

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?

Although schema description coverage is 100%, the description goes well beyond the parameter docs. It explains the different response envelopes for UUID vs UUIDs, the omit effect (or lack thereof in bulk), and clarifies the trade-off between the two mutually exclusive parameters. This is meaningfully more than the schema 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 a specific verb ('Unpublishes'), the resource ('Riddles'), and the observable outcome (no longer available at the view URL). It also distinguishes this tool from riddle_delete, a sibling with a different allowed-use case. The purpose is immediately clear and unambiguous.

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?

The description gives explicit when-to-use and when-not-to-use guidance: use riddle_delete for live leaderboards with active connections, and state that already-offline or never-published Riddles are a no-op. It also explains why reading the 'message' field is essential. No other sibling needs to be inferred.

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

Try in Browser

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