UGCBuilder

View saved version →

---
name: account-and-downloads
description: Check UGCBuilder account status, inspect generation status, and retrieve existing image or video download links without creating new generations.
---

Use get_account for current credits and generation prices. Report returned values accurately; do not rely on remembered balances or pricing.

For a known prepared request ID, call get_landing_page_request. For a known job ID, use get_generation or display_generation. If the user requests recent outputs without an ID, use list_generations and match the requested product or generation. Ask a concise clarification only if multiple results remain ambiguous.

List results are temporary in-memory jobs, not durable account history. Download links expire after 15 minutes. Jobs and links may disappear after server restarts. Share the exact returned downloadMarkdown or download URLs promptly, along with expiry when supplied. Never invent links or call a paid generation tool to replace expired results without a new user request and the required credit authorization.

Saving to Google Drive or another destination requires its available integration and an authorized destination. Do not claim files were saved because a download link was displayed.

View saved version →

---
name: landing-page-images
description: Create product landing-page section images with the UGCBuilder MCP. Use for UGCBuilder landing pages, product creative sections, or adapting supplied copy into landing-page images.
---

Use the connected UGCBuilder MCP and its current advertised tool schemas. Authenticate through the client's OAuth connection flow; never ask for passwords or embed tokens in files. If connection is required, present the connection flow.

Preserve the user's supplied product image, exact approved copy, language or dialect, section order, aspect ratio, and offer. Do not replace an explicit image reference. Prefer the attached product image when the tool accepts it. Chat attachments are not public HTTPS URLs; never invent image URLs. Ask only for genuinely missing required inputs.

For a complete page without a supplied structure, use Hero, Before & After, Ingredients / Features, Authority / Trust, How to Use, and Social Validation. Adapt ingredients to components/features where appropriate. Use custom section types for sections without a native mapping. Do not invent reviews, endorsements, certifications, scarcity, medical outcomes, or product facts. Frame before/after around supportable use cases. Respect requested Moroccan Darija, RTL hierarchy, and copy formatting.

Prefer prepare_landing_page for one or multiple sections. Supply the original requirements and exact requested copy in userBrief, with a product-specific design prompt for every section. Maintain consistent colors, typography, product identity, and visual hierarchy. The card collects format and total-credit approval and starts generation. Preparing the card does not spend credits; do not ask a separate format or budget question before opening it. Do not additionally call generate_landing_page for sections submitted through that card.

Use direct generate_landing_page only with a user-selected supported aspect ratio and sufficient explicit credit authorization for the entire requested set. Check current account prices when needed; never infer a credit budget from a request alone. Reuse the exact idempotency key and identical arguments for a retry. Do not retry an uncertain charge as a new request.

Use get_landing_page_request for prepared-request status, or get_generation for direct jobs. Immediately share returned downloadMarkdown as sections complete, with the expiry time. Poll direct jobs no more often than every 10 seconds. Retrieve existing jobs when the user asks for links; do not regenerate. Explain actual failure or expiry without claiming success. These outputs are section images, not published HTML websites. Use a separate authorized workflow if a working website is requested.

View saved version →

---
name: ugc-videos
description: Generate UGC product videos through UGCBuilder from a product image, scene direction, and dialogue.
---

Use current UGCBuilder MCP schemas and OAuth connection flow. Preserve supplied product references, script, dialect, character requirements, and duration. When drafting dialogue, use the requested language and only supported product claims.

Call generate_ugc_video with the product attachment or public HTTPS image URL, full script, requested duration, and appropriate scene/character direction. Use high quality; do not substitute Standard or Grok. Pass the full requested dialogue and desiredDurationSeconds. Requests above 7 seconds use extensions, with the full cost shown in the card. Use the current tool's supported duration limits and pricing. The interactive card collects portrait/landscape selection and approval for the full total. It starts generation after approval; do not call again to start or duplicate the job.

Reuse request keys for retries with identical inputs. Use the returned request ID with get_landing_page_request to check status when needed. Share returned downloadMarkdown promptly. Never claim generation completed while approval is pending, and never spend additional credits merely to retrieve downloads.