Skip to main content
Glama

Create landing page

create_landing_page

Create a hosted landing page shell with CDN, SSL, aggregate analytics, forms, and versioning. ランディングページ・LP・ホームページ・Webサイト・キャンペーンページの作成。

Where a page goes: a workspace holds sites, and each of its pages is a path on one of them: <name>.convika.page, or the workspace's own domain once its pages open there (get_brand shows them). Pass path, such as /guides/how-to-choose, to put the page there. Leave path out and the first page sits at /, a later one at a free path made from its name. subdomain is only for the workspace's first page: it names the workspace's convika.page site. For a full URL on a domain, such as https://www.example.com/lp2, pass url instead of path. Do not turn a requested path into a Convika subdomain.

After creation, use save_page_content to add HTML, then create_preview so the user can review it before production. Do not call publish_site unless the user explicitly asks to publish or go live.

If guidance.existingSite is present, the requested URL shows or forwards to another site now, and connecting it would replace that. Tell the user before any DNS change, as the text says.

This tool is equivalent to create_site — use either one.

New pages per UTC day, per workspace: Free 10, Pro 100, MAX 1000. The count resets at midnight UTC and includes pages created through the dashboard, uploads, built-in AI, MCP, and free tools. Deleting a page does not restore the day's allowance.

Input Schema

NameRequiredDescriptionDefault
urlNoOptional exact custom URL requested by the user, for example 'https://www.example.com/' or 'https://www.example.com/lp2'. If provided, Convika assigns this URL to the page after creating it. A root URL such as 'https://example.com/lp2' goes on 'https://www.example.com/lp2', and example.com redirects to www once its DNS points at Convika (guidance.rootRedirect has the records). If the reply has guidance.rootNotServed instead, example.com without www won't open the page.
nameYesDisplay name for the page (e.g. 'Spring Campaign 2026')
pathNoThe page's path on the workspace's site, such as '/guides/how-to-choose' or '/menu': lowercase letters, numbers, and hyphens between slashes. For a page after the first, write one: 1 to 3 English words that say what the page is, even when the page is in Japanese (料金表 → /pricing). Left out, Convika makes a free path from the name (the first page sits at /). Not together with url.
localeNoLanguage for the page content. Defaults to 'en' (English)en
purposeNoPurpose of the landing page (e.g. 'awareness', 'consideration', 'conversion', 'retention')
industryNoIndustry of the landing page (e.g. 'saas', 'ec', 'service', 'event', 'general')
subdomainNoOnly for the workspace's first page, while get_brand has no hostLabel: it names the workspace's site, <subdomain>.convika.page, and this page sits at /. Lowercase letters, numbers, and hyphens. Later pages share that site: give them path instead. Never put a requested path such as /lp2 here.
primaryOfferNoThe main offer or CTA promise, such as a free trial, demo, consultation, or purchase. Saved on the page; get_site returns it.
productSummaryNoWhat the page promotes, in one or two sentences. Saved on the page; get_site returns it.
targetAudienceNoWho the page is for, in one sentence (e.g. 'office workers near Shibuya station'). Saved on the page; get_site returns it.
expectedBrandIdNoThe workspace's id from get_brand. When the connection now works on another workspace (the dashboard's active workspace was switched), the call changes nothing and answers brand_mismatch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • changedInput schema / properties / expectedBrandId / description
      Previous value: -"The brand's id from get_brand. When the connection now works on another brand (the dashboard's active workspace was switched), the call changes nothing and answers brand_mismatch."New value: +"The workspace's id from get_brand. When the connection now works on another workspace (the dashboard's active workspace was switched), the call changes nothing and answers brand_mismatch."
    • changedInput schema / properties / locale / description
      Previous value: -"Language for the site content. Defaults to 'en' (English)"New value: +"Language for the page content. Defaults to 'en' (English)"
    • changedInput schema / properties / name / description
      Previous value: -"Display name for the site (e.g. 'Spring Campaign 2026')"New value: +"Display name for the page (e.g. 'Spring Campaign 2026')"
    • changedInput schema / properties / path / description
      Previous value: -"The page's path on the brand's address, such as '/guides/how-to-choose' or '/menu': lowercase letters, numbers, and hyphens between slashes. For a page after the first, write one: 1 to 3 English words that say what the page is, even when the page is in Japanese (料金表 → /pricing). Left out, Convika makes a free path from the name (the first page sits at /). Not together with url."New value: +"The page's path on the workspace's site, such as '/guides/how-to-choose' or '/menu': lowercase letters, numbers, and hyphens between slashes. For a page after the first, write one: 1 to 3 English words that say what the page is, even when the page is in Japanese (料金表 → /pricing). Left out, Convika makes a free path from the name (the first page sits at /). Not together with url."
    • changedInput schema / properties / primaryOffer / description
      Previous value: -"The main offer or CTA promise, such as a free trial, demo, consultation, or purchase. Saved on the site; get_site returns it."New value: +"The main offer or CTA promise, such as a free trial, demo, consultation, or purchase. Saved on the page; get_site returns it."
    • changedInput schema / properties / productSummary / description
      Previous value: -"What the page promotes, in one or two sentences. Saved on the site; get_site returns it."New value: +"What the page promotes, in one or two sentences. Saved on the page; get_site returns it."
    • changedInput schema / properties / subdomain / description
      Previous value: -"Only for the workspace's first page, while get_brand has no hostLabel: it names the brand's address, <subdomain>.convika.page, and this page sits at /. Lowercase letters, numbers, and hyphens. Later pages share that address: give them path instead. Never put a requested path such as /lp2 here."New value: +"Only for the workspace's first page, while get_brand has no hostLabel: it names the workspace's site, <subdomain>.convika.page, and this page sits at /. Lowercase letters, numbers, and hyphens. Later pages share that site: give them path instead. Never put a requested path such as /lp2 here."
    • changedInput schema / properties / targetAudience / description
      Previous value: -"Who the page is for, in one sentence (e.g. 'office workers near Shibuya station'). Saved on the site; get_site returns it."New value: +"Who the page is for, in one sentence (e.g. 'office workers near Shibuya station'). Saved on the page; get_site returns it."
    • changedInput schema / properties / url / description
      Previous value: -"Optional exact custom URL requested by the user, for example 'https://www.example.com/' or 'https://www.example.com/lp2'. If provided, Convika assigns this URL to the site after creating it. A root URL such as 'https://example.com/lp2' goes on 'https://www.example.com/lp2', and example.com redirects to www once its DNS points at Convika (guidance.rootRedirect has the records). If the reply has guidance.rootNotServed instead, example.com without www won't open the page."New value: +"Optional exact custom URL requested by the user, for example 'https://www.example.com/' or 'https://www.example.com/lp2'. If provided, Convika assigns this URL to the page after creating it. A root URL such as 'https://example.com/lp2' goes on 'https://www.example.com/lp2', and example.com redirects to www once its DNS points at Convika (guidance.rootRedirect has the records). If the reply has guidance.rootNotServed instead, example.com without www won't open the page."
  2. Changed1 schema field changed
    • changedInput schema / properties / path / description
      Previous value: -"The page's path on the brand's address, such as '/guides/how-to-choose' or '/menu': lowercase letters, numbers, and hyphens between slashes. Leave it out for a free path made from the name (the first page sits at /). Not together with url."New value: +"The page's path on the brand's address, such as '/guides/how-to-choose' or '/menu': lowercase letters, numbers, and hyphens between slashes. For a page after the first, write one: 1 to 3 English words that say what the page is, even when the page is in Japanese (料金表 → /pricing). Left out, Convika makes a free path from the name (the first page sits at /). Not together with url."
  3. Changed5 schema fields changed
    • addedInput schema / properties / expectedBrandId
      Added value: +{
      +  "description": "The brand's id from get_brand. When the connection now works on another brand (the dashboard's active workspace was switched), the call changes nothing and answers brand_mismatch.",
      +  "maxLength": 100,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / path
      Added value: +{
      +  "description": "The page's path on the brand's address, such as '/guides/how-to-choose' or '/menu': lowercase letters, numbers, and hyphens between slashes. Leave it out for a free path made from the name (the first page sits at /). Not together with url.",
      +  "maxLength": 200,
      +  "type": "string"
      +}
    • changedInput schema / properties / subdomain / description
      Previous value: -"Managed Convika fallback subdomain. Do not use this as a replacement for a user-requested custom URL path. Lowercase alphanumeric and hyphens only."New value: +"Only for the workspace's first page, while get_brand has no hostLabel: it names the brand's address, <subdomain>.convika.page, and this page sits at /. Lowercase letters, numbers, and hyphens. Later pages share that address: give them path instead. Never put a requested path such as /lp2 here."
    • changedInput schema / properties / url / description
      Previous value: -"Optional exact custom URL requested by the user, for example 'https://www.example.com/' or 'https://www.example.com/lp2'. If provided, Convika assigns this URL to the site after creating the fallback subdomain. A root URL such as 'https://example.com/lp2' goes on 'https://www.example.com/lp2', and example.com redirects to www once its DNS points at Convika (guidance.rootRedirect has the records). If the reply has guidance.rootNotServed instead, example.com without www won't open the page."New value: +"Optional exact custom URL requested by the user, for example 'https://www.example.com/' or 'https://www.example.com/lp2'. If provided, Convika assigns this URL to the site after creating it. A root URL such as 'https://example.com/lp2' goes on 'https://www.example.com/lp2', and example.com redirects to www once its DNS points at Convika (guidance.rootRedirect has the records). If the reply has guidance.rootNotServed instead, example.com without www won't open the page."
    • changedInput schema / required
      Previous value: -[
      -  "name",
      -  "subdomain"
      -]New value: +[
      +  "name"
      +]
  4. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"Optional exact custom URL requested by the user, for example 'https://www.example.com/' or 'https://www.example.com/lp2'. If provided, Convika assigns this URL to the site after creating the fallback subdomain. A root URL such as 'https://example.com/lp2' goes on 'https://www.example.com/lp2'; unless the reply has guidance.rootRedirect, example.com without www won't open the page (guidance.rootNotServed)."New value: +"Optional exact custom URL requested by the user, for example 'https://www.example.com/' or 'https://www.example.com/lp2'. If provided, Convika assigns this URL to the site after creating the fallback subdomain. A root URL such as 'https://example.com/lp2' goes on 'https://www.example.com/lp2', and example.com redirects to www once its DNS points at Convika (guidance.rootRedirect has the records). If the reply has guidance.rootNotServed instead, example.com without www won't open the page."
  5. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"Optional exact custom URL requested by the user, for example 'https://www.example.com/' or 'https://www.example.com/lp2'. If provided, Convika assigns this URL to the site after creating the fallback subdomain."New value: +"Optional exact custom URL requested by the user, for example 'https://www.example.com/' or 'https://www.example.com/lp2'. If provided, Convika assigns this URL to the site after creating the fallback subdomain. A root URL such as 'https://example.com/lp2' goes on 'https://www.example.com/lp2'; unless the reply has guidance.rootRedirect, example.com without www won't open the page (guidance.rootNotServed)."
  6. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, it discloses important behavior: daily per-workspace page quotas by plan, UTC reset timing, that deleted pages do not restore allowance, and that URL assignment may replace an existing site route when guidance.existingSite is present. It also clarifies the post-creation workflow.

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 long but justified by the tool's 11 parameters and routing rules. It is mostly front-loaded and organized, though the Japanese marketing line and some repeated routing details add minor noise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex creation tool with no output schema, the description is highly complete: it covers URL/path/subdomain behavior, quotas, follow-up tools, publishing caution, and the existingSite warning. An agent has enough context to invoke it correctly.

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?

Schema description coverage is 100%, so the baseline is 3, but the description adds useful integrated semantics for path, subdomain, and url: first page vs later pages, workspace site naming, and not putting a requested path into subdomain. Other parameters are already well documented in the schema.

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 opening sentence states a specific verb and resource: creating a hosted landing page shell with CDN, SSL, analytics, forms, and versioning. It also explicitly says the tool is equivalent to create_site, which helps an agent distinguish it from sibling creation tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives detailed when-to-use guidance: choose path vs url vs subdomain, use save_page_content after creation, then create_preview before production, and avoid publish_site unless the user explicitly asks. It also flags the guidance.existingSite case and tells the agent to warn before DNS changes.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.