Skip to main content
Glama

Quote a video with motion clips

quote_video
Read-onlyIdempotent

The exact credit price of a video with AI motion clips BEFORE it is made, and whether this account may make it. Read-only: nothing is created, reserved or charged, and no prompt is checked. approxUsd is totalCredits in USD at what a credit costs this account, and approxUsdBasis says how it is worked out. Returns baseCredits (the normal video), motionCredits (115 credits per motion scene, each a 5-second clip, on top of the normal video price), totalCredits, the balance and whether it covers the total, maxMotionScenes and, when it cannot be made, code + reason (MOTION_CLIPS_DISABLED: the feature is switched off). There is no plan or trial limit: enough credits is the only account condition. Motion scenes that cannot be made fall back to a still image with their credits refunded. Pass the same motion_scenes to create_video. Requires the "video:read" scope.

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

Input Schema

NameRequiredDescriptionDefault
languageNoOptional BCP-47 code (e.g. "en", "fa"). A language only ElevenLabs speaks adds its voice premium to baseCredits.
motion_scenesNoHow many scenes to price as AI clips (default 1).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds substantial context: nothing is created, reserved or charged, no prompt is checked, no plan or trial limit applies, motion scenes that cannot be made fall back to a still image with credits refunded, and the video:read scope is required. That is exactly the behavioral detail annotations cannot carry.

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?

Dense but front-loaded: the price-and-eligibility purpose comes first, then the read-only guarantee, then the return fields, then the create_video handoff and scope. Every sentence carries information an agent needs; nothing is padding.

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

Completeness5/5

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

No output schema exists, and the description compensates by enumerating the returned fields (baseCredits, motionCredits, totalCredits, balance, coverage, maxMotionScenes, code+reason) and explaining the MOTION_CLIPS_DISABLED failure code. For a two-parameter read-only quote tool, nothing material is missing.

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?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: motion_scenes defaults to 1 and is priced at 115 credits per 5-second scene on top of the base video, and language can add an ElevenLabs voice premium to baseCredits. This goes beyond the schema's field descriptions.

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

Purpose5/5

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

States a specific verb and resource ('exact credit price of a video with AI motion clips') plus the pre-creation timing and eligibility check. It also implicitly separates itself from create_video by telling the agent to pass the same motion_scenes there, so an agent can tell quote from create without opening either schema.

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?

Clear context: use it BEFORE the video is made, and the returned motion_scenes should be reused with create_video. It does not explicitly name quote_motion_clip or state when to prefer that sibling, so the alternative routing is left to inference.

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