ozor-url-to-video

Ozor URL-to-Video

End-to-end web-page-to-video on Ozor.ai. Hand Ozor a URL, get a plan back that reflects the actual page content (headlines, value props, social proof, CTA), approve or edit, and ship a finished video.

When to use

Use this skill when the input is a URL. Signals:

• "Make a video from https://..."
• "Video from my landing page / homepage / product page"
• "Turn this blog post into a video"
• "Video from this article / changelog page"
• Any message that contains a URL the user expects you to read

Do NOT use this skill when:

• Input is a short text brief → ozor-generate
• Input is an attached local file (PDF/PPTX/DOCX) → ozor-document-video
• User wants a written prompt only → ozor-landing-page-to-video (prompt-only skill)
• User wants to manage existing videos → ozor-video-library

Required MCP tools

• mcp__ozor__analyze_document — accepts a url parameter directly; no upload needed
• mcp__ozor__get_plan / mcp__ozor__update_plan — review/edit the plan before generation
• mcp__ozor__generate_from_plan — kicks off the build, returns projectId
• mcp__ozor__wait_for_job — if the response includes a jobId
• mcp__ozor__export_video, mcp__ozor__wait_for_export
• mcp__ozor__get_embed_code

If the MCP isn't connected, tell the user and stop. Do not browse the URL yourself and hand-write a prompt — Ozor extracts brand colors, hero imagery, and structure directly from the page. Your scraped text would lose that.

Workflow

Step 1 — Hand the URL to Ozor

mcp__ozor__analyze_document({
  url: "<the URL>",
  ...optional hints: targetDuration, format, audience, tone, focus
})

For URLs:

• Landing pages / product pages → default to format: "9:16" or "16:9" (ask if not obvious — vertical is great for social, landscape for embedding on the site itself), targetDuration: "30s"–"45s", tone "confident".
• Blog posts / articles → format: "16:9", targetDuration: "60s"–"90s", tone "informative".
• Changelog / release pages → format: "16:9", targetDuration: "30s"–"45s", tone "energetic", focus "one scene per shipped feature".
• Documentation pages → format: "16:9", targetDuration: "60s", tone "clear, technical", focus "explain what this feature does and how to use it".