Skip to main content
Glama

Turn any public website URL into a detailed prompt (layout, components, colors,

clone_ui
Read-only

Turn any public website URL into a detailed prompt (layout, components, colors, typography, spacing) for recreating its UI with a code model such as Lovable, v0, Claude or Cursor. Returns text, not code. Takes 10-30 s. Price: $0.05 per call (x402, USDC on Base). Without payment, returns the payment requirements.

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": {
      "url": "<url>"
    },
    "name": "clone_ui"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL
paymentNox402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.
access_keyNoOptional. Access key of a pack bought by card on https://www.aypiai.online (cs_live_...).
payment_txNoOptional. Base tx hash of a direct 0.05 USDC transfer to 0x4b1965f9d407ce9f032e9e2465afe7ff8bfb7f3d (single use).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / access_key / description
      Previous value: -"Optional. Access key of a pack (cs_live_...)."New value: +"Optional. Access key of a pack bought by card on https://www.aypiai.online (cs_live_...)."
    • addedInput schema / properties / payment
      Added value: +{
      +  "description": "x402 payment: the base64 PAYMENT-SIGNATURE value signed for the requirements returned by an unpaid call (USDC on Base, gasless). Omit on the first call to get the price and requirements.",
      +  "type": "string"
      +}
    • changedInput schema / properties / payment_tx / description
      Previous value: -"Optional. Base tx hash of a 0.25 USDC payment (single use)."New value: +"Optional. Base tx hash of a direct 0.05 USDC transfer to 0x4b1965f9d407ce9f032e9e2465afe7ff8bfb7f3d (single use)."
    • changedInput schema / properties / url / description
      Previous value: -"Public http(s) URL to recreate, e.g. https://stripe.com"New value: +"Public http(s) URL"
  2. First observed

TDQS

A4.2/5.0
Behavior5/5

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

With annotations only covering readOnly and openWorld, the description carries real weight: it discloses latency (10-30 s), cost ($0.05 per call, x402/USDC on Base), and explicitly what happens on an unpaid call (returns the payment requirements). It also clarifies the return type is text, not code.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense paragraph, front-loaded with what it produces and the return type, followed by latency and price. No filler sentences and every clause carries information an agent needs before spending money.

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?

No output schema exists, so the description correctly states the return format is text and explains the payment handshake. It stops short of covering edge cases such as JS-rendered sites, non-public URLs, or whether a paid call can fail and be refunded.

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?

All four parameters are fully documented in the schema, so the schema does the heavy lifting. The description adds the price figure that gives the payment_tx amount meaning and the two-step unpaid-then-paid sequence, but nothing about URL constraints or access_key precedence beyond what the schema already says.

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: turns a public website URL into a detailed UI prompt covering layout, components, colors, typography and spacing. It also scopes the output ("Returns text, not code") and names the consuming tools, so it is clearly distinguishable from extraction siblings like design_tokens or screenshot.

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

Usage Guidelines3/5

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

Usage context is implied by the stated purpose (feeding a code model) and the payment flow (omit payment on first call to get requirements), but the description never says when to prefer this over sibling tools that also analyze a page's design or markup, and lists no exclusions.

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.