OrgLines

Website: Switch template

website_switch_template

Destructive

Switch an existing landing to another template (layout of blocks for a kind of business, e.g. it, service, beauty, expert, home_repair, device_repair), keeping the owner's content: blocks the new template adds arrive hidden, blocks it drops are hidden, a version is saved first. Premium on a free workspace → status 'blocked' with 'upsell'. Runs propose→confirm. CONFIRMATION: this tool is PROPOSED, never performed directly. You get status='confirmation_required' with an action_id and a plan_token, and the write happens only after confirm_action.

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": {
      "template": "<template>"
    },
    "name": "website_switch_template"
  }
}

Input Schema

Name	Required	Description
`style`	No
`palette`	No
`website`	No	Site id, name or subdomain. Optional when the workspace has one site.
`template`	Yes	Template (archetype) slug; an unknown one returns the list.
`direction`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Adds substantial behavior beyond the annotations: content is preserved, added blocks arrive hidden, dropped blocks are hidden, a version is saved first, and a premium template on a free workspace returns status 'blocked' with an upsell. It also spells out that the tool never writes directly and returns status='confirmation_required' with plan_token — exactly the context destructiveHint alone cannot convey.

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 purpose then effects then the confirmation contract — a sensible order. The CONFIRMATION sentence and the following line are partially redundant, but the repeated warning is defensible for a destructive, two-step tool.

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?

For a destructive mutation with no output schema, the description covers the mutation's effects, the two-phase commit requirement, the terminal statuses ('confirmation_required', 'blocked'), and the failure/upsell path. An agent has everything needed to call it and interpret the response.

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 only 40% schema coverage, the description compensates for the most important parameter by enumerating valid template archetypes, and it clarifies the premium/free-workspace interaction that implicitly maps to style. Palette, direction, and website remain unexplained beyond the schema, so it does not fully close the gap.

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 ('Switch an existing landing to another template') and immediately glosses what a template is with concrete archetype examples (it, service, beauty, home_repair). An agent can distinguish this from list/status/style siblings without opening another 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 clear operating context: it applies to an existing landing, is a propose→confirm operation, and routes the follow-up to confirm_action with an action_id/plan_token. It does not, however, state when NOT to use it (e.g. for a brand-new site via website_create_landing) or contrast it with website_set_style.

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

All OrgLines 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?