Skip to main content
Glama

Tiquiz Quiz Funnel

List quizzes

list_quizzes
Read-onlyIdempotent

List the quizzes, scored quizzes, surveys and Popquiz video quizzes of the connected Tiquiz account, newest first. Each item has its status (active = live, draft = not live, trash = deleted and restorable for 30 days), its public URL, its workspace, and lifetime key figures (views, starts, completions, leads). Use it first to find a quiz id, or to answer 'how are my quizzes doing overall'. For figures over a period or compared to the previous one, call get_stats. It never returns lead data.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_quizzes"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoFilter by content type. 'quiz' includes scored quizzes.all
limitNo
statusNo'active' = live, 'draft' = not live (never published or switched off), 'trash' = deleted, restorable for 30 days. 'all' excludes the trash.all
project_idNoOnly this workspace (PLUS plans can have several). Omit for the whole account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description's added value is the return shape (status, public URL, workspace, lifetime views/starts/completions/leads) and the important exclusion 'it never returns lead data', plus the 30-day trash restorability. It stops short of describing pagination or how to page beyond `limit`, which is the only meaningful behavior left undisclosed.

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

Conciseness4/5

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

Front-loaded with purpose and ordering, then routing, then the caveat, all in four dense sentences. Slight waste in re-explaining status values that the schema already documents, but nothing is bloated.

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?

No output schema exists, so the description carries the burden of describing the returned fields, and it does so (status, URL, workspace, lifetime metrics) plus the explicit lead-data exclusion. For a four-optional-parameter read-only listing tool, an agent has what it needs to call it correctly.

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 coverage is 75% and the description largely restates semantics already present in the schema's enum descriptions (status definitions, quiz including scored quizzes). It adds nothing about `limit` (the one undocumented parameter) or about using `kind`/`project_id` as filters. Baseline 3 is appropriate.

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?

Specific verb plus resource, and it enumerates the content types covered (quizzes, scored quizzes, surveys, Popquiz video quizzes) and the ordering (newest first). An agent can distinguish this from get_quiz and get_stats without opening a schema.

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?

Gives explicit when-to-use triggers ('use it first to find a quiz id', 'how are my quizzes doing overall') and names the alternative plus the condition that selects it ('for figures over a period or compared to the previous one, call get_stats').

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.

Resources