Skip to main content
Glama
Sign In

Instant Business Website Builder & Next.js Generator

by io.github.AGI-CEO
OverviewDiscussionsAdmin

redesign_existing_website_url

Instantly redesign and upgrade any existing WordPress, Wix, Squarespace, GoDaddy, or PHP website into a modern, blazing-fast Next.js App Router website. Scrapes the existing URL's branding, services, and copy and returns a live interactive Next.js preview link.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe existing website URL to scrape and redesign into Next.js (e.g., 'https://example.com').
abVariantNoPricing variant: 'A' ($0 Free Setup + $29/mo), 'B' ($49 Setup + $19/mo), or 'C' ($29/mo Flat).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses the scraping behavior (branding, services, copy are pulled from the URL), the transformation target, and that the return is a preview link. It leaves gaps on permissions, latency/failure behavior (the word 'Instantly' is a claim, not a guarantee), and whether the preview is persistent.

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?

Two tightly written sentences: the transformation and supported platforms are front-loaded, and the outcome/return is stated second. No filler, no repetition of the tool name.

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?

For a two-parameter tool with full schema coverage and no output schema, the description supplies what the schema cannot: the transformation pipeline and the shape of the result (a live preview link). It could go further on prerequisites (site must be publicly reachable) and processing time, but nothing essential to a correct invocation is missing.

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 description coverage is 100%, so both parameters (url and abVariant with its enum pricing tiers) are already fully documented in the schema. The description adds no syntax, format, or constraint detail beyond what the structured fields provide, so the baseline of 3 applies.

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 pair ('redesign ... existing WordPress, Wix, Squarespace, GoDaddy, or PHP website into ... Next.js'), names the supported source platforms, and specifies the outcome (a live interactive Next.js preview link). The word 'existing' implicitly separates it from the sibling generate_instant_business_website.

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 is implied by 'existing URL' and the platform list, so an agent can infer this is for migrating/refreshing a site that already exists. However, there is no explicit when-to-use or when-not, and it never names generate_instant_business_website as the alternative for greenfield sites.

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

All Instant Business Website Builder & Next.js Generator toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources