Skip to main content
Glama

zapcap_mcp_get_templates

Retrieve available video processing templates from ZapCap to configure automated workflows for content creation and editing tasks.

Instructions

Get available templates from ZapCap

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function that executes the tool logic, returning a static dictionary with information on how to access templates via the ZapCap dashboard.
    def zapcap_mcp_get_templates() -> Dict[str, Any]:
        return {
            "result": {
                "templates_url": "https://platform.zapcap.ai/dashboard/templates",
                "message": "Templates are available in the ZapCap dashboard with preview images",
                "instructions": "1. Visit the dashboard URL above\n2. Browse templates with visual previews\n3. Copy the template ID for use in create_task",
                "note": "Templates include various caption styles, animations, and layouts"
            }
        }
  • Registers the zapcap_mcp_get_templates tool with the FastMCP server instance.
    @mcp.tool(description="Get available templates from ZapCap")
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. The description only states what the tool does ('Get available templates') without explaining what 'templates' are, how they're returned, whether this is a read-only operation, or any rate limits or authentication requirements. For a tool with zero annotation coverage, this is insufficient behavioral context.

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?

The description is a single, efficient sentence that states the core purpose without unnecessary words. It's appropriately sized for a simple tool with no parameters. However, it could be slightly more structured by front-loading key information about what 'templates' represent.

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?

Given the tool has no parameters, an output schema exists, and annotations are absent, the description is minimally complete. It identifies the resource ('templates') but doesn't explain what templates are or their format. The output schema will handle return values, but the description could better contextualize what 'available templates' means in this system.

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?

The tool has 0 parameters with 100% schema description coverage. The description doesn't need to explain parameters since none exist. The baseline for 0 parameters is 4, as the description appropriately doesn't waste space on non-existent parameters.

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

Purpose3/5

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

The description states the tool's purpose as 'Get available templates from ZapCap', which is a clear verb+resource combination. However, it doesn't differentiate this tool from its siblings (create_task, monitor_task, upload_video, upload_video_by_url), which all involve different operations. The purpose is understandable but lacks sibling context.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, timing considerations, or relationships to sibling tools. Without any usage context, the agent must infer when this tool is appropriate.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bogdanminko/zapcap-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server