JustCopy

Change a website

change_site

Changes an existing website as described in plain words ("add our Saturday hours", "make the booking form ask for the dog's breed", "use a darker green"). The change runs in the background: this tool returns at once and get_site reports the result. Changes after a site's first build are part of the paid plans; on the free plan get_site reports needs_upgrade with an upgradeUrl. Cost: one of the day's builds on paid plans; not available on the free plan.

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": {
      "siteId": "<siteId>",
      "request": "<request>"
    },
    "name": "change_site"
  }
}

Input Schema

Name	Required	Description	Default
`siteId`	Yes	The site id from list_sites or create_site.
`request`	Yes	The change, in plain words.

Output Schema

Name	Required	Description	Default
`name`	Yes
`next`	Yes
`siteId`	Yes
`status`	Yes
`studioUrl`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations by disclosing that the operation is asynchronous (returns immediately, result via get_site), that it consumes a build credit on paid plans, that it is unavailable on the free plan, and that get_site will report needs_upgrade with an upgradeUrl. This is exactly the cost/async/plan context an agent needs before invoking a mutation.

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 what the tool does and the examples, then the async behavior, then billing. Four sentences all carry information, though the billing detail is slightly dense and could be tightened.

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 an output schema present, return values need not be explained, and the async/polling model plus plan-gating is fully spelled out. Nothing an agent needs in order to call it correctly and interpret the outcome is missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning by illustrating what the freeform `request` string should contain (plain-words change instructions) rather than structured fields. `siteId` provenance is already covered in 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 (changes), resource (an existing website), and clarifies the input modality with three concrete plain-language examples. Clearly distinguishes itself from create_site by scoping to existing sites.

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?

Explicitly routes the agent: the call returns at once and get_site reports the result, so polling behavior is clear. It also states plan gating (paid plans only after first build). It does not explicitly say 'use create_site for new sites', but the 'existing website' scoping makes that inference easy.

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

All JustCopy tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?