Skip to main content
Glama

nucleo-site-options-set

Idempotent

Saves WordPress site title, tagline, homepage, posts page, date and time formats, business schema, icons and modern image formats, validating every value before anything is written.

Instructions

Saves the site title, tagline, homepage, posts page, date and time formats, the business shown in the structured data, the site icons and the modern image formats (avif, webp). Pages are given by slug and must be published. Every value is checked before anything is written.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nucleo-site-options-set"
  }
}

Input Schema

NameRequiredDescriptionDefault
iconsNoSite icons for nc/icon: name (a-z, 0-9, -) → SVG markup. The whole set is replaced. Colors become currentColor, so the icon takes the color style of the block. Scripts, styles, links and unknown elements are removed. A name of a built-in icon replaces it. To add or remove single icons use nucleo-icons-set.
titleNoSite title. Plain text.
taglineNoSite tagline. Plain text.
businessNoThe business behind the site, printed as schema.org JSON-LD on the homepage and on pages whose meta.seo.schema uses "@business". Keys are schema.org names: @type (default LocalBusiness, e.g. AutoPartsStore), name (required), legalName, vatID (e.g. IT01234567890), taxID, description, url, logo, image, telephone, email, address {streetAddress, addressLocality, addressRegion, postalCode, addressCountry}, geo {latitude, longitude}, openingHours (list such as "Mo-Fr 08:00-18:00"), foundingDate, areaServed, sameAs (list of URLs), priceRange. null removes it. Not printed when Yoast or Rank Math is active.
homepageNoSlug of a published page for the static homepage, or null for the latest posts.
siteIconNoFavicon and app icon (WordPress site_icon): URL of an image in the media library, square, at least 512×512 px. Upload it first with nucleo-media-upload. null removes it.
postsPageNoSlug of a published page that lists the posts, or null for none.
dateFormatNoPHP date format of the site, e.g. "j F Y" (27 ottobre 2026) or "d/m/Y".
timeFormatNoPHP time format of the site, e.g. "H:i".
imageFormatsNoModern image formats generated next to the uploaded images: "avif", "webp" or both, in order of preference. Empty list turns them off. Optional: the original stays the fallback of <picture>. Files are generated on upload; existing images need nucleo-media-formats.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false. The description adds one genuinely useful behavior beyond that: all values are validated before any write, implying an all-or-nothing update. It does not say what happens to omitted keys (merge vs. reset) or what a validation failure returns, which matters for a 10-parameter optional-only 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?

Three sentences, front-loaded with the resource and its field set, ending with the validation guarantee. The long enumeration is dense but each clause maps to real parameters; nothing reads as filler.

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 10-parameter, all-optional mutation with nested objects and no output schema, the description covers coverage of what is written and the validation guarantee but omits partial-update semantics, error behavior, and a pointer to nucleo-site-describe for reading current state. Adequate but with clear gaps.

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 the per-field detail (including the published-slug requirement) is already in the schema. The description's only parameter-adjacent addition is restating that pages are given by slug and must be published, which duplicates the schema rather than extending it.

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 names a clear verb+resource ('Saves the site title, tagline, homepage, ...') and enumerates the settings surface, so an agent knows this is a site-options write, not a content write. It does not differentiate from close siblings such as nucleo-settings-set, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the field list: the note that pages are given by slug and must be published is the one real precondition. There is no statement of when to prefer this over nucleo-settings-set, or that nucleo-site-describe should be used first to read current values.

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