Skip to main content
Glama

Browse VidGuy templates

browse_templates
Read-onlyIdempotent

Browse a VidGuy template catalog. source "remix": clips where one person is replaced by the user's own (Remix / character swap). source "faceless": looks for faceless what-if shorts. Returns each template's id, name and description plus howToUse, the tools that turn one into a video; hosts that support MCP Apps also show the user a clickable gallery with previews. FREE and read-only: browsing or the user highlighting a template never authorizes a generation. Search with query (every word must match); page with offset. A source that isn't open on the account returns an error saying so.

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": {
      "source": "<source>"
    },
    "name": "browse_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoTemplates per page (default 30).
queryNoWords to match in the name, description or tags. Omit to browse.
offsetNoPass nextOffset from the previous page.
sourceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds meaningful context on top: it is FREE, browsing or the user highlighting a template never authorizes a generation, and MCP-App-capable hosts render a clickable gallery. The error behavior for a closed source is disclosed. It does not state the pagination/nextOffset contract explicitly, which is the only real behavioral gap.

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?

Front-loads the resource and both source definitions, then returns, then constraints—no filler sentences. Some clauses are packed into long semicolon-joined runs (the return/gallery sentence), which slightly hurts scanability but every sentence 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 describes the return fields and the host-dependent gallery rendering, plus the error case and cost/no-authorization guarantee. Complete for a read-only browse tool; only the nextOffset-based paging contract is left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 75%, and the description fills the most important hole: the source enum values are given concrete meaning ("remix" = character swap, "faceless" = faceless what-if shorts), which the schema's bare enum does not convey. It also adds AND-matching semantics for multi-word queries and frames offset as paging, beyond the schema's wording.

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?

Uses a specific verb and resource ("Browse a VidGuy template catalog") and clearly separates the two catalog sources, remix vs faceless, with a one-line meaning for each. An agent knows exactly what it retrieves and the shape of the return (id, name, description, howToUse). It does not explicitly contrast itself with the sibling list_carousel_templates, so it stops short of full sibling differentiation.

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?

Gives concrete when-to-use guidance for each source and for the two optional behaviors: search with query (every word must match) and page with offset. It also states the failure condition (a source not open on the account returns an error), which is real operational guidance. No alternative tool is named, so it lacks explicit routing away from siblings.

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