Skip to main content
Glama

list_quizzes

Read-onlyIdempotent

Retrieve quizzes in an organization filtered by exact name or updated-after timestamp; use cursor pagination to continue until no more pages remain.

Instructions

Find quizzes in this organization, by name or by when they last changed.

    Returns ONE PAGE. Check `has_more` - if it is true there are more quizzes than
    you can see, and you must call again with `next_cursor` before telling the user
    how many exist or that one is absent.

    `filter_name` is an EXACT match, case-insensitive - a partial name returns
    nothing. `filter_updated_since` needs an ISO-8601 timestamp WITH a timezone
    offset; a naive one is rejected.

    Returns settings only, not questions - use `list_questions` with `filter_quiz_id`
    for those. Requires the `quizzes:read` OAuth scope.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
page_sizeNo
filter_nameNo
page_cursorNo
filter_updated_sinceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
noteYes
quizzesYes
has_moreYes
next_cursorNo
Install Server

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already mark this as read-only, idempotent, and non-destructive. The description adds valuable behavioral context beyond annotations: it returns only one page, requires cursor-based pagination, has exact-match filtering semantics, rejects naive timestamps, and returns settings but not questions. This fully discloses the tool's behavioral quirks.

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 well-structured, front-loading the core purpose before moving to pagination, filters, and exclusions. Every sentence adds necessary operational detail without redundancy.

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 the tool's complexity, the description covers everything an agent needs to call it correctly: pagination behavior, filter constraints, timestamp format requirements, scope requirements, and the boundary with list_questions. The presence of an output schema also covers return values, so nothing essential is missing.

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 0%, so the description carries the burden of explaining parameters. It explains filter_name (exact, case-insensitive, partial returns nothing), filter_updated_since (ISO-8601 with timezone), and next_cursor usage. page_size is only implied through 'one page' and has_more, so one minor param lacks detailed semantics, but overall compensation is strong.

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 uses a specific verb and resource: 'Find quizzes in this organization,' and further clarifies what it returns ('settings only, not questions'). It also distinguishes itself from list_questions by directing the user there for questions, making it easy to tell apart from sibling tools.

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 usage guidance: filter_name is exact-match and case-insensitive, filter_updated_since requires an ISO-8601 timestamp with timezone offset, and pagination must be handled with has_more and next_cursor. It also names the alternative tool (list_questions) for question content and notes the required OAuth scope.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CloudSecurityAlliance/csa-skilljar'

If you have feedback or need assistance with the MCP directory API, please join our Discord server