Skip to main content
Glama
ViralFaceVideo Template Finder

ViralFaceVideo Template Finder

Find ViralFaceVideo templates

find_video_templates
Read-only

Find photo-to-video templates by photo count and English keywords, returning preview pages, clip durations, and credit costs so you can compare options before choosing.

Instructions

Find photo-to-video templates by photo count and English keywords. Returns official preview pages, durations, and credit costs.

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

Input Schema

NameRequiredDescriptionDefault
queryNoEnglish keywords, such as dance, celebration, or rap
photosNoNumber of photos available

Output Schema

NameRequiredDescriptionDefault
templatesYes
catalogUrlYes

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?

The readOnlyHint and openWorldHint annotations already establish that this is a safe, read-only search over an open catalog. The description adds that results carry preview pages, durations, and credit costs, but says nothing about result limits, ranking, or how queries are matched, and no destructive or auth behavior is described or needed.

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 well-formed sentences, front-loaded with the core purpose and with no filler. The second sentence slightly duplicates what the output schema already conveys, which keeps it from being maximally tight.

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 an output schema present and annotations covering the safety profile, the description only needs to convey purpose and filtering intent, which it does. Minor gaps remain around result ranking/limits and whether both parameters are optional in practice.

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 100%, so both the keywords and photo-count parameters are already fully documented, including the English-language constraint and the allowed values 1 or 2. The description only restates those parameters in summary form and adds no syntax or behavioral detail beyond the schema.

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 uses a specific verb ("Find") and resource ("photo-to-video templates") and states the two filtering dimensions, so an agent knows exactly what the tool retrieves. No sibling tools exist to differentiate against, so it cannot reach a 5.

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 or when-not-to-use guidance, nor any stated prerequisites or alternatives. The filtering criteria describe the tool's inputs rather than the situations that should select it, leaving usage implicit.

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

Deploy Server

Other Tools