Skip to main content
Glama

questionBank_getItems

Read-onlyIdempotent

Lists the items (draft content) of a question bank, optionally filtered by search term, blockType, category or difficultyRange - the same filters the Creator's question bank grid offers. Also reads a built-in template from questionBank_templateList, which is how to preview a template's actual questions before deciding to duplicate it - pass page/pageSize there, a template can hold tens of thousands of items and is returned in full otherwise. Deliberately unlike questionBank_list: omitting page/pageSize here returns everything rather than defaulting to a page, since a bank you filled yourself is often small enough that "everything" is the right answer - an invalid page/pageSize (zero, negative, non-numeric, fractional, or a pageSize over 100) is rejected outright rather than silently clamped.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number, starting at 1. Omit (with pageSize also omitted) to return every matching item at once - not what you want on a big bank or a template, which hold thousands of items; unlike questionBank_list, this tool never paginates on its own. Zero, negative, non-numeric or fractional is rejected, not rounded.
searchNoSearch term to filter items by their column values (e.g. the question title or a choice).
categoryNoFilter items to only this category.
pageSizeNoItems per page, only used together with page - given alone it is taken as page 1, not ignored (default: 50, max: 100). Same validation as page; over 100 is rejected, not clamped.
blockTypeNoFilter items to only this block type (e.g. "SingleChoice").
questionBankIdYesThe ID of the question bank to list items of - an own bank, or a built-in template from questionBank_templateList to preview its questions.
difficultyRangeNoFilter items to a difficulty range, as [min, max] (e.g. [1, 5]). Omit for no difficulty filter.

TDQS

A4.9/5.0
Behavior5/5

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

Even with readOnlyHint and idempotentHint annotations, the description adds substantial behavioral context: omitting pagination returns everything rather than defaulting to a page, invalid page/pageSize values are rejected rather than clamped, templates can hold tens of thousands of items and are returned in full otherwise. This goes well beyond the annotations and helps the agent anticipate tool behavior accurately.

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 three dense sentences, front-loaded with the core purpose, then filters, then the template and pagination nuances. Every sentence contributes useful information and there is no filler or repetition of the schema text.

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?

Given 7 parameters, no output schema, and the availability of strong annotations and schema descriptions, this description covers all important selection and invocation concerns: what the tool returns conceptually, how filters relate to the grid, the special template use case, and the precise pagination contract. It is complete enough for an agent to decide when and how to call it.

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 description coverage is 100% and each parameter is already well documented, so the baseline is 3. The description adds extra semantic value by explaining that the filters mirror the Creator's question bank grid, that questionBankId can be a built-in template for previewing questions, and why page/pageSize behave differently here than in questionBank_list—this meaningfully enriches the schema definitions.

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 a specific verb and resource: 'Lists the items (draft content) of a question bank' and then names the optional filters. It explicitly distinguishes itself from the sibling questionBank_list and from questionBank_templateList by clarifying that it can also preview template questions, making its purpose and scope immediately clear.

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 provides strong when-to-use guidance: use this tool for question bank items or to preview a built-in template before duplicating it, and it explicitly contrasts its pagination behavior with questionBank_list. It tells the agent when to pass page/pageSize (for large templates) and when to omit them (small own banks), which is actionable and complete.

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

A3.8/5.0
Disambiguation4/5

Tools are largely distinct by name and detailed descriptions, with clear prefixes (riddle_builder_*, questionBank_*, stats_*). Some potential confusion exists among the stats tools (stats_fetch vs stats_overview_fetch vs breakdowns) but descriptions clarify their different scopes. Overall, an agent can usually pick the right tool.

Naming Consistency4/5

Naming follows a predictable prefix+verb pattern within each domain (e.g., riddle_builder_quiz, riddle_builder_poll; riddle_get, riddle_publish). Minor inconsistencies exist, like the camelCase 'questionBank' and 'riddleTemplate' prefixes vs snake_case elsewhere, and 'stats_overview_fetch' ordering, but these are not chaotic and remain readable.

Tool Count1/5

With 62 tools, this far exceeds the recommended 3-15 range and even the 25+ threshold. While the server covers a broad domain, the extreme number overwhelms and makes tool selection harder, fitting the 'extreme mismatch' criterion for 50+ tools.

Completeness5/5

The tool surface is exceptionally comprehensive, covering creation, reading, updating, deleting, publishing, unpublishing, moving, tagging, template management, question banks, palettes, and various stats breakdowns. There are no obvious gaps in the lifecycle of managing interactive content, and all apparent operations are supported.

Resources