Skip to main content
Glama

Postclick by PPC.io: Landing Page CRO and AI Page Builder

Download a built page as files

export_page
Read-onlyIdempotent

Uses no credits. Packages a finished page as a zip that runs on any static host: index.html with every image it uses pulled into assets/, plus a README and metadata.json. Returns a download link. This is the one for a user who wants the files. share_page is the one for a user who wants something to look at. It also returns implementation_prompt: step by step instructions for putting this page live on the user's own site. Postclick hosts a built page only for a live test, which the user starts in the app, so this is how a page goes live for good. If you have access to their site, you can carry those steps out yourself; otherwise hand the prompt to whoever does. Pass platform when you know where the site lives, because the steps for WordPress and for Webflow are genuinely different. Ask if you do not know. The builder variants stop at a draft and never publish without the user confirming.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "build_run_id": "<build_run_id>"
    },
    "name": "export_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNoWhere the page goes live. "host" is the simplest for any site: the page on its own subdomain (go.example.com) at a web host such as Hostinger, Netlify or Vercel, and the zip's CLAUDE.md holds every step. Omit if unknown and the instructions will assume nothing.
build_run_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / platform / description
      Previous value: -"Where the user's site lives. Omit if unknown and the instructions will assume nothing."New value: +"Where the page goes live. \"host\" is the simplest for any site: the page on its own subdomain (go.example.com) at a web host such as Hostinger, Netlify or Vercel, and the zip's CLAUDE.md holds every step. Omit if unknown and the instructions will assume nothing."
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "wordpress",
      -  "webflow",
      -  "framer",
      -  "wix",
      -  "squarespace",
      -  "shopify",
      -  "other"
      -]New value: +[
      +  "host",
      +  "wordpress",
      +  "webflow",
      +  "framer",
      +  "wix",
      +  "squarespace",
      +  "shopify",
      +  "other"
      +]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare this read-only, idempotent, non-destructive and open-world, so the safety bar is covered. The description still adds real context beyond the annotations: no credits are consumed, the exact contents of the zip, the download-link return, and a second return value (implementation_prompt) with instructions on what to do with it. It does not state link expiry, zip size limits, or whether re-exporting an identical build reruns work.

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 key differentiation and output contents are front-loaded, which is correct. Some sentences are looser than needed — the Postclick-hosting explanation and the closing note about builder variants stopping at a draft are wordy and slightly tangential to the decision to export, though they do carry some context.

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?

With no output schema, the description carries the burden and largely meets it: it describes both returned artifacts and what to do with them, plus the deployment context that motivates the tool. It falls short only on build_run_id semantics and on lifecycle details of the download link.

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 50%: the platform enum is well documented in the schema, and the description mostly restates it (pass platform when known, ask if unknown), adding only the behavioral directive that WordPress and Webflow steps genuinely differ. The required build_run_id has no description in either the schema or the prose, so the description does not fully compensate for the coverage gap.

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 names a specific action and artifact: packages a finished page as a zip running on any static host, containing index.html, assets/, README and metadata.json, and returns a download link. It explicitly separates itself from sibling share_page ("share_page is the one for a user who wants something to look at"), so an agent can route between them without opening either schema.

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?

It gives an explicit use case (the user wants the actual files, not a viewable preview), an explicit alternative (share_page), and explains why export exists at all — Postclick only hosts a built page for a live test, so export is the path to permanent hosting. It also tells the agent to carry out the returned steps when it has site access and to hand the prompt off otherwise, and to ask the user for platform when unknown.

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.

Resources