Skip to main content
Glama

Outil.io

List video assets

list_video_assets
Read-only

Rechercher les médias vidéo/audio existants dans le projet courant, avec pagination. Inspecter le média avant de choisir les bornes source.

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

Input Schema

NameRequiredDescriptionDefault
qNo
kindNovideo
pageNo
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered by structured data. The description adds that results are scoped to the current project and paginated, but says nothing about result shape, ordering, or that results default to video only.

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?

Two short sentences, front-loaded with the action and scope, with no wasted wording. The second sentence earns its place as a workflow hint, though it could be folded into the first.

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?

For a read-only, non-destructive list tool with annotations covering safety and no output schema, the essentials are present. Still missing are the default kind filter and any indication of what the returned assets contain, which matters for a tool whose whole purpose is inspection.

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 description coverage is 0%, so the description must carry the load; it partially does by implying a search term ("Rechercher"), a video/audio filter, and pagination covering page/limit. It omits meaningful semantics such as the kind parameter defaulting to "video" and the 100-item limit cap, leaving gaps on a 4-parameter tool.

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 gives a specific verb and resource: searching existing video/audio media within the current project, with pagination. It is clear enough to separate this listing tool from export- or project-level siblings, but it never names an alternative to disambiguate further.

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?

"Inspecter le média avant de choisir les bornes source" gives a workflow hint about when this lookup precedes a downstream selection step, which is real guidance. However, there are no explicit when-not conditions and no named alternative tool for related listing tasks.

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.