Zambo AI Tools

video_create

Generate a complete video production package from any idea — script, shot list, scene descriptions, camera directions, and camera-ready prompts for RunwayML, Kling, Pika, and Sora. Claude cannot make videos natively. This bridges the gap — get everything you need to create any video in minutes using free tools. Returns: full timestamped script, shot-by-shot breakdown, director notes, an optimized prompt per free platform, and a keyframe preview image. 3 free/day. Zambo Pass: unlimited.

Input Schema

TableJSON Schema

Name	Required	Description
`style`	No	Visual style: 'cinematic', 'documentary', 'social', 'commercial', 'explainer', 'music_video', 'vlog'. Default: social.
`concept`	Yes	What the video should be about. Example: 'a 30-second ad for a new AI dev tool, dark theme, hype energy'
`aspect_ratio`	No	Aspect ratio: '16:9' (YouTube/desktop), '9:16' (TikTok/Reels/Shorts), '1:1' (Instagram). Default: 9:16.
`duration_secs`	No	Target duration in seconds. Default 30. Range: 5–120.

TDQS

A4.1/5.0

Behavior4/5

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

No annotations provided, so the description carries full burden. It discloses output details (script, shot list, prompts), limitations (3 free/day), and workflow context (bridges Claude's inability to create videos). It lacks info on authentication or rate limits beyond daily cap.

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 paragraph but front-loads the main purpose. It covers outputs, limits, and context without redundancy. Could benefit from bullet points for readability, but overall concise.

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?

Given no output schema, the description compensates by listing return values. It also explains the tool's role relative to Claude's capabilities and mentions free tier limits. Lacks error handling or edge case info, but sufficient for typical use.

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 coverage is 100% and all parameters have clear descriptions. The description adds context about the tool's purpose and outputs but does not enhance parameter understanding beyond the schema's own 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?

The description clearly states the tool generates a 'complete video production package', listing specific outputs like script, shot list, and prompts. This distinguishes it from sibling tools like image_generate by focusing on video pre-production rather than asset generation.

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?

The description explains when to use the tool (when you need to plan a video using AI, since 'Claude cannot make videos natively') and includes usage limits ('3 free/day'). However, it does not explicitly mention when not to use it or suggest alternative tools.

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

All Zambo AI Tools tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.5/5.0

Disambiguation3/5

Many tools have distinct purposes, but there are several overlapping or redundant tools (e.g., leadsignal vs leadsignal_generate, multiple code audit tools, multiple trading proposal/journal tools, and several 'universal' entry points like zambo_help, zambo_ask, zambo_universal). Descriptions help, but the volume creates ambiguity.

Naming Consistency3/5

Naming conventions vary across prefixes (zambo_, zambot_, axis_, presence_, trading_, etc.), with some tools using single words (weather, translate) and others using verb_noun patterns. Aliases like leadsignal_generate for leadsignal break consistency. While prefixes provide some grouping, the overall pattern is mixed.

Tool Count2/5

125 tools is excessive for a single MCP server, even if the server aims to be a universal stack. This makes it overwhelming for agents to navigate and increases the likelihood of misselection. Many tools could be split into domain-specific servers.

Completeness5/5

The tool surface is extraordinarily comprehensive, covering agent identity, cross-layer orchestration, code analysis, content generation, legal scanning, lead generation, trading, on-chain data, and more. Nearly any common agent task is supported with multiple tools, leaving few obvious gaps.

Resources

Need Help?