Skip to main content
Glama

Website: put the approved site live

website_launch
Destructive

Put the client's approved website live on its domain. Call WITHOUT confirm first: the checklist shows what's ready (approved, domain verified, the quote form connected to a hosted lead form, tracking) and the redirects every old address needs, with suggestions. Pass redirects for every old page that had search clicks. Then confirm: true charges hosting ($25/month per site, on the card the agency's plan uses, from today) and publishes it; once the CNAME points here the domain serves it. Tracking ids (not code) go in tracking.

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": {
      "client": "<client>"
    },
    "name": "website_launch"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientYes
confirmNoLeave false to preview: nothing changes and the preview shows exactly what would happen. Set true only after the user has agreed to this exact change.
trackingNo
redirectsNoOld address → new page, e.g. {from: '/cedar-fencing.html', to: '/cedar-fences'}

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already flag destructive, non-idempotent, open-world behavior, and the description adds substantial context beyond them: the $25/month per-site hosting charge billed from today on the agency plan's card, the CNAME requirement for the domain to serve, and what the preview reveals. It stops short of saying whether publishing can be undone or what happens on partial failure, which keeps it below a 5.

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-loads the action and the preview-then-confirm sequence, and every clause carries information (cost, billing source, CNAME, tracking format). It is dense and slightly run-on, but no sentence is wasted.

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, and the description does describe what the preview returns (readiness checklist, redirect suggestions), which is the key return value. Cost and domain-serving conditions are covered; failure modes and reversibility are the remaining gap for a destructive, non-idempotent tool.

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?

With 50% schema coverage, the description compensates well: it clarifies that tracking takes ids not code snippets, that redirects should cover every old page with search clicks, and that confirm gates the charge and publish. The 'client' parameter and the 300-item redirect cap are left to 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?

States a specific verb and resource ('put the client's approved website live on its domain') and implicitly distinguishes itself from siblings like website_approve and website_domain by naming the approved-state and domain-serving preconditions.

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?

Gives an explicit two-step protocol: call without confirm first to see the readiness checklist and redirect suggestions, then set confirm: true only after agreement. It also states the rule for redirects ('every old page that had search clicks'), leaving little to inference.

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.