---
name: sparklaunch-landing-pages
description: >
  Use when a connected SparkLaunch user needs to create, generate, publish,
  inspect, or measure landing pages with the landing.* tools. Do not use for
  generic web design advice without a SparkLaunch landing-page operation.
---

# SparkLaunch Landing Pages

Create and operate conversion-focused SparkLaunch landing pages.

## Connection And Scope

<!-- sparklaunch:connection:start -->
1. Use the SparkLaunch MCP connection supplied by Cursor. Never ask the user for credentials, access tokens, refresh tokens, client secrets, or authorization headers.
2. If the SparkLaunch tools are absent, stop before planning or claiming execution and say: **SparkLaunch isn't available in this Cursor session. Open Customize, confirm that the SparkLaunch plugin and MCP server are installed and enabled, and follow Cursor's authentication prompt if shown. Then reload the Cursor window or start a new Agent conversation and send the request again.**
3. If a SparkLaunch tool returns an OAuth challenge, ask the user to complete Cursor's SparkLaunch authentication prompt, then retry only after the connection succeeds.
4. If authorization is expired or revoked, stop before any write and say: **Your SparkLaunch authorization is expired or revoked. Re-authenticate SparkLaunch from Cursor's Customize page, complete the permission screen, and then retry. I will not repeat a write until the connection is restored and any uncertain prior result is checked.**
<!-- sparklaunch:connection:end -->
5. Resolve the project with `projects.list`, then pass `project_id` to every landing tool. Use `projects.get` to confirm `effective_permissions` includes `landing.write` before proposing or confirming a write; explain a plan or role limitation without requesting OAuth reconnection.
6. Use stable, unique `idempotency_key` values for `landing.create_project` and `landing.generate_content`. A generation call without `landing_project_id` returns an unsaved preview. To replace the selected private draft, repeat the generation intent with `landing_project_id` through its confirmation preview and verify `saved_to_draft=true`.
7. `landing.publish` changes public internet state. Its first call returns a confirmation preview naming the landing page, slug, preview URL, and exact public destination; show it and wait for explicit approval before repeating the exact call with the same key and returned `confirmation_token`.
8. Never automatically retry an uncertain publish.
9. Retain project, landing-page, lead, and draft identifiers and versions only as internal tool-call state. Never repeat them to the user or include identifier/version labels or columns; refer to landing pages by name, slug, or URL.

## Workflow

1. Gather product name, one-liner, target customer, template type, CTA type, and desired proof signal.
2. Call `landing.create_project`.
3. Call `landing.generate_content` without `landing_project_id` to create an unsaved structured-copy preview and present it to the user.
4. If the user wants that direction saved, call `landing.generate_content` with the selected `landing_project_id`, show the draft-replacement preview, and wait for approval before the confirmed call. Verify `saved_to_draft=true` and retain the returned draft version and preview URL.
5. Review the saved draft preview, then ask whether the user wants the exact public destination published.
6. Call `landing.publish` through its separate public-state confirmation flow.
7. Verify the public state with `landing.get_project` before sharing the production URL.
8. Use `landing.get_analytics` and `landing.get_leads` for evidence-backed follow-up.

Template types: `saas`, `marketplace`, `ai_tool`, `waitlist`. CTA types: `waitlist`, `book_call`, `newsletter`.

The tool can replace a draft only with the complete content returned by `landing.generate_content`; it does not expose arbitrary field-level draft patches, logo selection, or favorite selection. Do not claim those narrower changes were made.

## Output

For projects, report name, slug, status, template, CTA, preview URL, production URL, and publish time when present. For analytics, report views, clicks, submissions, time window, and trend data. For leads, reveal only the records the user requested.