Skip to main content
Glama

video_info

Read-only

Retrieve every setting, size, length, file path, and watch link for a single video to inspect its details before editing or re-rendering.

Instructions

Everything about one video: all its settings, size, length, path and a link to watch it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "video": "<video>"
    },
    "name": "video_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
videoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 safety is covered by structured data. The description's contribution is listing the returned fields (settings, size, length, path, watch link), which is useful given there is no output schema, but it says nothing about behavior when the video does not exist or is still processing.

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?

A single front-loaded sentence with no filler; the scope ('one video') comes first and the enumerated payload follows. Every clause carries information.

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 usefully previews the returned content, and the annotations cover the safety profile. What remains missing is any hint about the identifier format and edge-case behavior, which is small but real for a one-parameter lookup tool.

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?

Schema description coverage is 0% for the single required 'video' parameter, so the description must carry the meaning. It only says 'one video', without specifying whether the value is an ID, filename, URL, or path, or what format is expected.

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 states a specific verb-and-resource combination ('everything about one video') and enumerates what that includes: settings, size, length, path and a watch link. It is clearly a read-metadata tool, distinguishable from write-oriented siblings like build_video or delete_video, though it never names a sibling it is meant to replace.

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

Usage Guidelines2/5

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

There is no explicit when-to-use statement, no prerequisite, and no mention of alternatives such as get_defaults or get_logs. The intended usage (inspect a single existing video) is only implied by the word 'one video'.

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