Swebsy

Update settings

swebsy_update_settings

Update site settings — SEO title/description, site URL, structured data (JSON-LD), per-page SEO overrides, language/direction, theme tokens (light + dark), type scale, animation defaults, Google and uploaded fonts, dark mode toggle, site-wide custom CSS for component-level restyling (globalTheme.customTailwindConfig), favicon, robots.txt/sitemap/service worker/security headers/image optimization (performance), analytics ids, custom head/body code (advanced), the "Made with Swebsy" badge (branding) and the deploy target (deploy). Provide ONLY the fields that change. general/seo are SITE-WIDE; use page to change ONE page. Also used to match the theme to a reference IMAGE's vibe: sample its palette into brand/surface tokens and ALWAYS set BOTH light and dark variants.

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": {
      "summary": "<summary>"
    },
    "name": "swebsy_update_settings"
  }
}

Input Schema

Name	Required	Description
`seo`	No	SITE-WIDE SEO. `siteUrl` is what makes robots.txt/sitemap.xml and canonical/og:url real — without it they ship the `https://yoursite.com` placeholder and the site is not indexable.
`page`	No	SEO for the CURRENTLY SELECTED PAGE ONLY — the per-page overrides otherwise reachable just from the Pages panel. Use this whenever you mean one page: `general.title`/`general.description` are SITE-WIDE and setting them to fix one page silently rewrites the meta description of every other page. Each field overrides its site-wide counterpart for this page; omit a field to keep inheriting. Pass `null` as the whole object to clear every override.
`fonts`	No	Fonts to add/replace. Each array you pass replaces what was there, so send the full desired list; an omitted array is kept.
`deploy`	No	Deploy target configuration. API tokens are never settable here: the user pastes them in Settings → Deployment. Send only the keys that change.
`favicon`	No	Set the favicon from one square image. Upload it with `upload_asset` first (PNG or SVG, at least 512x512), then pass its asset id. Every size (16px up to 512px, Apple touch, Android, MS tile) is generated from it.
`general`	No
`summary`	Yes	1 sentence explaining the settings change.
`advanced`	No	RAW site code, the last resort. Use globalTheme.customTailwindConfig for CSS and seo.jsonLd for structured data. Each field REPLACES the previous value, so read the current settings and send the full code. It runs on every visitor's page, and the Studio warns the user about any agent change that can run script (all of it except plain CSS).
`branding`	No	The "Made with Swebsy" badge. Turning it off only takes effect on plans that include badge removal; free plans keep the badge on export regardless.
`analytics`	No	Analytics ids — the snippet is generated from the id. Empty string removes one.
`globalTheme`	No	Theme overrides. Shallow diff — only include keys that change.
`performance`	No	Crawling files, service worker, security headers and export-time image optimization.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 9, 2026

changedInput schema / properties / advanced / description

Previous value: -"RAW site code, the last resort. Use globalTheme.customTailwindConfig for CSS and seo.jsonLd for structured data. Each field REPLACES the previous value, so read the current settings and send the full code. It runs on every visitor's page, and the Studio flags every agent change to it."New value: +"RAW site code, the last resort. Use globalTheme.customTailwindConfig for CSS and seo.jsonLd for structured data. Each field REPLACES the previous value, so read the current settings and send the full code. It runs on every visitor's page, and the Studio warns the user about any agent change that can run script (all of it except plain CSS)."

Changed1 schema field changedOct 28, 2026

changedInput schema / properties / globalTheme / properties / customTailwindConfig / description

Previous value: -"Raw CSS appended to the compiled stylesheet (canvas + export). Use for SITE-WIDE rules that utilities/tokens can't express — restyling a whole component type (e.g. make every `.btn` neobrutalist), custom box-shadows, border-width/radius. Colors MUST use theme vars (var(--color-neutral), var(--color-secondary)) so they stay dark-mode aware. This REPLACES the previous value — send the full CSS you want, not a fragment. This CSS is document-scoped: it does NOT travel into a harvested block, so it locks styled sections to this template. NEVER use it to build a repeated custom component (card, link block, tile) — make that a SYMBOL styled with theme classes so it stays harvestable. Reserve custom CSS for genuinely global polish only."New value: +"Raw CSS appended to the compiled stylesheet (canvas + export). Use for SITE-WIDE rules that utilities/tokens can't express — restyling a whole component type (e.g. make every `.btn` neobrutalist), custom box-shadows, border-width/radius. Colors MUST use theme vars (var(--color-neutral), var(--color-secondary)) so they stay dark-mode aware. This REPLACES the previous value — send the full CSS you want, not a fragment. This CSS is document-scoped: it does NOT travel into a harvested block, so it locks styled sections to this template. NEVER use it to build a repeated custom component (card, link block, tile) — make that a SYMBOL styled with theme classes so it stays harvestable. Reserve custom CSS for genuinely global polish only. NEVER set type here (font-family, font-size, font-weight, font-style, letter-spacing, line-height, text-transform) on a class: that text's type disappears from the style panel. Fonts go in typography.fontFamily roles (a second display face in the free role, e.g. mono, applied per element with font-mono); size/weight/italic/tracking/case are utility classes on the element. Only bare-element defaults (body, h1-h6, p) inside @layer components may set type."

First observedOct 19, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare this is a non-read-only but non-destructive mutation in a closed environment. The description adds partial-update semantics and scope behavior, but it does not surface the replacement/destructive side effects of fields like fonts, customTailwindConfig, or custom code—those warnings live in the schema instead.

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

Conciseness3/5

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

It is front-loaded with the tool's purpose, but the bulk is a dense run-on enumeration of nearly every settings category, much of which duplicates schema coverage. The key usage rules at the end are valuable but would be easier to scan with bullets or shorter grouping.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter, deeply nested settings tool with no output schema, the description covers purpose and the critical site-wide vs page scope distinction. However, it omits return behavior and does not reiterate important caveats such as full-array replacement or custom code execution, leaving the schema to carry those behavioral details.

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 92%, so the parameter documentation is already strong. The description adds cross-cutting meaning by differentiating site-wide `general`/`seo` from per-page `page` and by emphasizing that only changed fields should be sent, but it does not add much beyond the schema for individual parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Update site settings', then enumerates the categories of settings it touches (SEO, URL, fonts, theme, deploy). It is clear what the tool does, but it does not explicitly differentiate itself from siblings like swebsy_update_page or swebsy_rename_site beyond the general/seo vs page distinction.

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?

It gives actionable usage guidance: 'Provide ONLY the fields that change', 'general/seo are SITE-WIDE; use page to change ONE page', and a note about matching a reference image's palette. It lacks explicit when-not-to-use conditions or named alternatives for non-page settings, but the core usage context is clear.

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

All Swebsy tools Inspect

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

Need Help?