Ginta

Change a website

update_site

Destructive

Changes an existing site's pages: small find/replace edits (preferred), whole files, deleted files, or the form email; a change takes about 1–3 minutes. All changes apply together as one new version (undo with restore_version). note is required: what you changed and why. Photos: /_g/photo?q= gives real photos; image URLs written from memory are often fake, and ones that don't load are replaced.

Input Schema

Name	Required	Description
`note`	Yes	REQUIRED. 1–2 plain sentences: what you changed and why, e.g. "Rebuilt the menu page, added lunch prices, moved contact to the footer." The owner sees it in Ginta's editor; Ginta's own AI reads it.
`edits`	No	Find/replace edits (preferred).
`files`	No	Whole files to add or replace (only the changed ones).
`delete`	No	Paths of files to delete (not index.html).
`site_id`	Yes	The site id: the first part of the site URL, e.g. "bella-roma" for https://bella-roma.ginta.page (see list_sites).
`notify_email`	No	Another address for form messages ("" = back to the account email).

Output Schema

Name	Required	Description
`url`	Yes	The site's address.
`text`	Yes	The answer in words, the same as the text content: read it (for get_guide the whole guide, for get_site the files' contents).
`check`	Yes	Ginta's visitor check of the site: forms, parts, links.
`changed`	Yes	Files changed.
`deleted`	Yes	Files deleted.
`notices`	Yes	Sentences to tell the owner word for word.
`site_id`	Yes	The site id.
`version`	Yes	The new live version number.
`warnings`	Yes	Things to look at (the change was saved).
`notify_email`	Yes	Another address form messages go to, masked (null = the account email).
`images_swapped`	No	Outside images that didn't load and were replaced with Ginta photos.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 4, 2026

addedOutput schema / properties / text

Added value: +{
+  "description": "The answer in words, the same as the text content: read it (for get_guide the whole guide, for get_site the files' contents).",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "site_id",
-  "url",
-  "version",
-  "warnings",
-  "notices",
-  "check",
-  "changed",
-  "deleted",
-  "notify_email"
-]New value: +[
+  "site_id",
+  "url",
+  "version",
+  "warnings",
+  "notices",
+  "check",
+  "changed",
+  "deleted",
+  "notify_email",
+  "text"
+]

Changed1 schema field changedNov 2, 2026

changedOutput schema / properties / notify_email / description

Previous value: -"Where form messages go (null = the account email)."New value: +"Another address form messages go to, masked (null = the account email)."

Changed1 schema field changedOct 18, 2026

addedOutput schema / properties / images_swapped

Added value: +{
+  "description": "Outside images that didn't load and were replaced with Ginta photos.",
+  "items": {
+    "additionalProperties": {},
+    "properties": {
+      "path": {
+        "description": "The page or stylesheet.",
+        "type": "string"
+      },
+      "photo": {
+        "description": "The Ginta photo search put in its place (\"\" = removed, the image next to it shows).",
+        "type": "string"
+      },
+      "url": {
+        "description": "The image URL that didn't load.",
+        "type": "string"
+      }
+    },
+    "required": [
+      "path",
+      "url",
+      "photo"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

First observedOct 15, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations already flag destructive=true and idempotent=false, but the description adds substantial context beyond them: edits apply atomically as one new version, the operation takes 1-3 minutes, note is mandatory and owner-visible, and memory-written image URLs are often fake. This is exactly the extra behavioral detail annotations cannot express.

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 core action and change modes in the first clause, then layers constraints and undo path. The trailing photo/URL guidance is tangential to the tool's mechanics but earns its place by preventing a common failure mode; no sentence is pure filler.

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?

Complete for a destructive multi-mode mutation tool with full schema coverage and an output schema. Timing, atomicity, undo path, required note rationale, and image-sourcing caveat cover everything an agent needs before invoking it.

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 all six parameters are already documented in the schema, which sets a baseline of 3. The description adds only marginal meaning beyond that: the preference for edits and the purpose of note, both of which the schema also conveys. The photo URL pattern is useful but is guidance, not parameter semantics.

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 ('Changes an existing site's pages') and enumerates the exact change modes: find/replace edits, whole files, deletions, and form email. It also names a sibling by function ('undo with restore_version'), so an agent can separate this from rollback tooling without opening the 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 a clear preference signal ('small find/replace edits (preferred)') and routes undo behavior to restore_version. It stops short of explicit when-not guidance (e.g. when to use whole-file replacement instead of edits, or when preview_site is warranted first).

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

All Ginta tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?