Skip to main content
Glama

get_available_videos

Retrieve all videos available in VLC with their file paths so AI assistants can browse and select media for playback.

Instructions

Get all available videos with their path.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it only implies a read operation. It says nothing about whether 'available' means a configured media library, a filesystem scan, or a browse context, nor anything about cost or result size for an unrestricted enumeration. The output schema covers return values, but scope and read semantics remain 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?

A single short sentence with no filler and the most useful detail (that paths are included) front-loaded. It is efficient rather than padded, though it is on the terse side for a tool whose scope term is ambiguous.

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

Completeness3/5

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

The tool is simple, parameterless, and blessed with an output schema, so much of the burden is lifted. Still, the undefined scope of 'available' leaves an agent unsure whether this returns an entire media library or just the current browse location, which matters when choose between it and browse_folder.

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?

The tool takes zero parameters, so there is no parameter meaning the description needs to add and nothing the schema could be compensating for. Baseline 4 applies; the clause 'with their path' is the only payload-relevant detail.

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 ('get all available videos') plus the key returned attribute ('with their path'), which distinguishes it from siblings like get_tracks or get_playlist. The only weakness is that 'available' is never defined (library-wide? current folder? browsed path?).

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?

The word 'get' plus 'all' implies an unfiltered enumeration, which indirectly suggests this is the tool to call when you need a complete video list. There is no explicit when-to-use statement, no mention of browse_folder as the alternative for directory-scoped discovery, and no stated preconditions.

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