Skip to main content
Glama
Sign In

api

by video.quiz
OverviewDiscussionsAdmin

List your media library

quiz_video_list_media
Read-onlyIdempotent

List files you have uploaded, newest first, so a file can be re-used without uploading it again. URLs in the response are signed and expire within an hour.

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": "quiz_video_list_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the read-only, idempotent, and nondestructive annotations, it discloses newest-first ordering and that response URLs are signed and expire within an hour. These details materially affect how an agent should handle the results.

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?

Two short sentences front-load the operation and then supply useful reuse and URL-expiry details. There is no redundant or promotional wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read operation with two optional parameters, this is enough to make a basic call and handle returned URLs correctly. Optional-filter behavior, the default limit, and any pagination behavior remain undocumented, but these are modest gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Neither kind nor limit is mentioned despite 0% schema description coverage. The enum and numeric bounds make the parameters broadly inferable, but the description adds nothing about filtering, result-count behavior, or defaults.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the operation and resource: “List files you have uploaded,” with newest-first ordering and a reuse purpose. It does not explicitly distinguish this library from siblings such as quiz_video_list_music or quiz_video_get_quiz_media.

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?

The phrase “so a file can be re-used without uploading it again” provides a concrete when-to-use scenario. It does not explain when to use an upload, quiz-media, or music-listing sibling instead.

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

All api toolsInspect
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