Skip to main content
Glama

Change my website

editar_web

Use this when the person wants to change something on one of their palimpalem websites: texts, titles, photos, sections, new pages ("add a page about …", added to the menu, sitemap and llms.txt), colours and style, contact details, WhatsApp button, SEO title. Requires palimpalem sign-in. Takes the change in plain words, carries it out and says exactly what changed. To work on another page than the home page give page; to aim at one element give element (ids from ver_mi_web). To put an own photo of the person in place of an existing one give photo_url (a public https address of a JPG, PNG or WebP) and element (the id of the photo); photo_edit improves (light, colour, sharpness) or crops an own photo to fit its place. Changes are saved and visible right away; each one can be undone (also by asking to undo the last change, or with versiones_web). Translations follow automatically. Does not touch domain, e-mail, payments or the account. Takes 5 to 60 seconds.

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": {
      "web": "<web>"
    },
    "name": "editar_web"
  }
}

Input Schema

NameRequiredDescriptionDefault
webYesThe website: its name, its palimpalem address or its own domain.
pageNoOptional. The page to change (name from ver_mi_web, e.g. "menu"). Without it, the home page.
elementNoOptional. Element id from ver_mi_web (e.g. b12) to aim the change at. Required with photo_url and photo_edit (the id of the photo).
requestNoThe change in plain words, in any language, e.g. "Change the main title to Fresh bread every morning" or "Add a section with opening hours: Mon-Fri 8-14". Optional when only photo_url or photo_edit is given.
photo_urlNoOptional. Public https address of a photo (JPG, PNG or WebP, up to 15 MB) that replaces the photo at element. It is copied to the website.
photo_editNoOptional. improve: better light, colour and sharpness; fit: crop to the shape of its place around the main subject. Only for the website's own photos (also right after photo_url).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / element
      Added value: +{
      +  "description": "Optional. Element id from ver_mi_web (e.g. b12) to aim the change at. Required with photo_url and photo_edit (the id of the photo).",
      +  "type": "string"
      +}
    • addedInput schema / properties / page
      Added value: +{
      +  "description": "Optional. The page to change (name from ver_mi_web, e.g. \"menu\"). Without it, the home page.",
      +  "type": "string"
      +}
    • addedInput schema / properties / photo_edit
      Added value: +{
      +  "description": "Optional. improve: better light, colour and sharpness; fit: crop to the shape of its place around the main subject. Only for the website's own photos (also right after photo_url).",
      +  "enum": [
      +    "improve",
      +    "fit"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / photo_url
      Added value: +{
      +  "description": "Optional. Public https address of a photo (JPG, PNG or WebP, up to 15 MB) that replaces the photo at element. It is copied to the website.",
      +  "type": "string"
      +}
    • changedInput schema / properties / request / description
      Previous value: -"The change in plain words, in any language, e.g. \"Change the main title to Fresh bread every morning\" or \"Add a section with opening hours: Mon-Fri 8-14\"."New value: +"The change in plain words, in any language, e.g. \"Change the main title to Fresh bread every morning\" or \"Add a section with opening hours: Mon-Fri 8-14\". Optional when only photo_url or photo_edit is given."
    • changedInput schema / required
      Previous value: -[
      -  "web",
      -  "request"
      -]New value: +[
      +  "web"
      +]
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already flag a non-readonly, non-destructive, non-idempotent write, and the description adds real context beyond them: sign-in required, changes saved and visible immediately, each change undoable (directly or via versiones_web), translations applied automatically, and a 5–60 second runtime. The only gap is no mention of failure modes or partial-apply behaviour, so it stops short of the top mark.

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 the triggering condition and organized by decision (page → element → photo → behaviour → limits), so an agent can scan it quickly. It is dense and slightly long, with a few clauses that restate schema text, but no sentence is 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?

For a live-mutation tool with no output schema, the definition covers authentication, effect visibility, reversibility, timing, side effects on translations, and hard boundaries. Nothing an agent needs in order to invoke it correctly appears to be 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 schema already defines all six parameters; the description nonetheless adds cross-parameter guidance – element is required together with photo_url/photo_edit, and request is optional when only a photo parameter is supplied. That interaction logic is the main value added over the schema's per-field text, though much of the wording otherwise mirrors 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 ("change something on one of their palimpalem websites") and enumerates the concrete domains it covers: texts, titles, photos, sections, new pages, colours, contact details, WhatsApp button, SEO title. It also names the sibling read tool (ver_mi_web) for ids and versiones_web for undo, so an agent can separate it from neighbouring tools without opening a schema.

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 explicit selection logic: use page when the change is not on the home page, use element to aim at one element, give photo_url plus element to swap a photo, photo_edit to improve or fit. It also states exclusions outright – it does not touch domain, e-mail, payments or the account – which is exactly the when-not guidance most definitions lack.

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.