Skip to main content
Glama

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

Check how a page build is going

get_build
Read-onlyIdempotent

Uses no credits. Returns the build's status and, once finished, the complete page. A build takes about 10 to 20 minutes, so poll it with wait set to 300: the call holds open and returns the moment the stage moves or the page is ready, which turns a build from dozens of identical reads into a handful of calls that each have something to report. When a call comes back with the same stage you already mentioned, say nothing and call again rather than paraphrasing yourself. A status of running is non-terminal and contains no page. By default the HTML is summarised rather than returned in full, because a page is tens of thousands of characters and would flood the conversation. Set include_html when the user actually wants the file, for example to save it locally and open it. Includes elapsed_seconds: the true age of the build, measured server side from its start timestamp.

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": "get_build"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoSeconds to wait for a material change. Use 25 for broad client compatibility; longer waits are available for hosts that support them. A timeout preserves the run; resume by ID instead of starting again.
build_run_idYes
include_htmlNoReturn the full page HTML. Large. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations: no credit cost, 10-20 minute expected duration, long-poll hold-open semantics that return on stage change, non-terminal 'running' status carrying no page, and default HTML summarisation to avoid flooding. This is exactly the kind of context the annotations cannot express.

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?

Front-loaded with cost and return shape, then polling guidance, then the include_html decision. Slightly long, and the instruction about not paraphrasing yourself when a stage repeats is conversational guidance rather than tool semantics, but the rest earns its place.

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?

With no output schema, the description carries the return contract itself: status, conditional page, summarised vs full HTML, and elapsed_seconds. Nothing an agent needs in order to call and interpret this tool is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds real meaning beyond the 67%-covered schema: wait is explained as a hold-open that resumes by the same build_run_id rather than restarting, include_html is tied to the concrete user intent of saving/opening the file, and elapsed_seconds is described as server-side measured from build start.

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?

States a specific verb and resource ('Returns the build's status and, once finished, the complete page') and scopes it as a read-only poll of an in-flight build. An agent can distinguish this from build_page, which starts a build, 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 Guidelines4/5

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

Gives concrete operating guidance: poll with wait=300, set include_html only when the user wants the file. It does not explicitly name the sibling that starts a build or state 'do not use this to start one', so usage is strongly implied rather than exhaustively routed.

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