Riddle Quiz Maker

question_bank_list

Read-onlyIdempotent

Lists question banks. Scope "own" (the default) lists the banks of a project - the same ones the Creator shows; pass a projectId to look into another project, omit it for the project the API key is scoped to (your personal ones on a user API key). Paginated {items, page, pageSize, total, hasMore}. Scope "templates" lists the built-in starter banks instead - pre-filled banks anyone can copy with question_bank_manage(action: "duplicate") to get real content immediately instead of starting empty. It takes riddleType and nothing else (a handful of them, nothing to page or search) and answers with id, title, PUBLISHED "itemCount", DRAFT "draftItemCount", which blockTypes those items are (null when that cannot be told yet) and a few example categories out of "categoryCount". A template that was never published reports "itemCount": 0 however many questions it holds - judge its real size by "draftItemCount", the number a duplicate would give you, and read the chosen id with question_bank_get and question_bank_get_items before duplicating. Every write here rejects a template id: a template is only ever changed through a copy of it.

Input Schema

TableJSON Schema

Name	Required	Description
`page`	No	Page number (default: 1). Scope "own" only.
`tags`	No	Filter by tag IDs (array of integers), as returned by riddle_tag_list. Omit to ignore tags. Scope "own" only.
`scope`	No	What to list: "own" (default) for the question banks of a project, "templates" for the built-in starter banks anyone can duplicate.
`search`	No	Search term to filter banks by title. Scope "own" only.
`sortBy`	No	Sort field: "createdAt" or "modifiedAt". Defaults to "createdAt". Scope "own" only.
`pageSize`	No	Items per page (default: 12, max: 50). Scope "own" only.
`projectId`	No	The project (team) ID whose banks you want, as returned by project_list. Omit for the banks of the project the API key is scoped to (your personal ones on a user API key). Scope "own" only.
`sortOrder`	No	Sort direction: "ASC" or "DESC". Defaults to "DESC". Scope "own" only.
`riddleType`	No	Filter by Riddle type ("Quiz" or "Poll"). Omit to list banks of every type. Applies to both scopes.

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 2, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare this a safe, idempotent read, but the description adds genuinely non-obvious behavior: templates return a shape with id/title/itemCount/draftItemCount/blockTypes/categories, an unpublished template always reports itemCount 0 so draftItemCount is the real size, and every write rejects a template id. That is exactly the kind of caveat an agent cannot infer from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core scoping rule is front-loaded, but the paragraph is dense and repetitive — the projectId omission rule and the 'scope own only' constraints are restated from the schema, and the template paragraph packs several ideas into one run-on. It earns most of its length but not all of it.

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 carries the return-value burden and does so: it names the paginated envelope fields and the template-specific fields. For a 9-parameter, dual-scope list tool, an agent has everything needed to call it and interpret results.

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?

Schema coverage is 100%, so baseline is 3. The description still adds meaning beyond the schema: it frames riddleType as the only applicable parameter in 'templates' scope ('nothing else'), and reinforces the projectId/api-key scoping semantics rather than merely restating field types.

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?

States a specific verb and resource ('Lists question banks') and immediately distinguishes the two scopes it can operate in. An agent can tell it apart from question_bank_get and question_bank_get_items from the first sentence alone.

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?

Gives explicit conditions for choosing a scope (default 'own' vs 'templates'), when to pass projectId vs omit it, and routes the agent to question_bank_get and question_bank_get_items before duplicating. It does not compare against the other list siblings (e.g. riddle_template_list), so it falls short of a full when/when-not map.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?