Skip to main content
Glama

Singing Pet

List videos

list_videos
Read-onlyIdempotent

List this account's videos, newest first, with their status and download URLs.

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_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return. Defaults to 25.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world scope, so safety is covered. The description adds real context beyond that — newest-first ordering and that each item carries status and download URLs — but says nothing about result size ceilings or what happens when the account has more than the limit allows.

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?

One compact sentence that front-loads scope, then ordering, then payload. Nothing is wasted and nothing needs reordering.

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?

With no output schema, the description correctly takes on the job of saying what comes back (status and download URLs) and in what order. The only gap is behavior at the limit boundary, which the schema's maximum partially mitigates.

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?

Single optional parameter with 100% schema description coverage; the schema already documents the 1-100 bound and the default of 25. The description adds no meaning about limit or how it interacts with the fixed ordering, so this is baseline territory.

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?

States a specific verb and resource ("List this account's videos") plus ordering ("newest first") and returned fields, which clearly separates it from the mutation siblings like create_singing_video and delete_video. It stops short of naming the read alternatives (get_video_status, get_pet_song) it overlaps with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this is the enumeration tool and get_video_status is the per-item lookup, but the description never states when to prefer this over those siblings or any exclusions. No prerequisites or scoping conditions are given.

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