Skip to main content
Glama
alokemajumder

wpxmcp

by alokemajumder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Update site settings

update_site_settings

Update global WordPress site settings like homepage, timezone, date format, and registration. Changes apply immediately for all visitors and require administrator access.

Instructions

Update the site's core settings. These are global and take effect immediately for every visitor — changing show_on_front or page_on_front changes what the homepage is, and changing start_of_week or timezone shifts every displayed date. Requires an Administrator account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoSite title.
site_idNoWhich configured WordPress site to act on. Optional — with a single site configured it is used automatically; with several, the default site is used unless you name one. Run list_sites for valid ids.
languageNoSite locale, e.g. "en_GB".
timezoneNoA PHP timezone string, e.g. "Europe/London".
site_iconNoAttachment ID for the site icon / favicon.
date_formatNoPHP date format, e.g. "F j, Y".
descriptionNoTagline.
time_formatNoPHP time format, e.g. "g:i a".
page_on_frontNoPage ID to use as the front page. Only applies when show_on_front is "page".
show_on_frontNoWhether the front page shows the blog or a static page.
start_of_weekNo0 = Sunday.
page_for_postsNoPage ID that lists blog posts.
posts_per_pageNoHow many posts appear on a blog listing page.
default_categoryNoCategory ID assigned to posts with no category.
users_can_registerNoAllow public registration. Enabling this on a site without spam protection invites abuse.
default_ping_statusNoWhether new content accepts pingbacks and trackbacks.
default_post_formatNoPost format applied to new posts, e.g. "standard".
default_comment_statusNoWhether new content allows comments by default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / default_category / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / default_category / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / page_for_posts / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / page_for_posts / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / page_on_front / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / page_on_front / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / posts_per_page / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / site_icon / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / site_icon / minimum
      Added value: +-9007199254740991
  2. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

The description discloses meaningful behavior beyond the annotations: changes are global, take effect immediately for every visitor, and specific settings alter the homepage or displayed dates. The Administrator requirement adds useful authorization context. Nothing here contradicts the readOnlyHint=false, destructiveHint=false, or idempotentHint=false annotations.

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

Conciseness5/5

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

Three front-loaded sentences with no filler: the operation, the high-impact implications, and the auth requirement. Every sentence earns its place, and the most important caveats appear immediately.

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

Completeness4/5

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

For an 18-parameter, zero-required tool with full schema coverage, the description covers global impact, immediacy, and authentication. It does not describe the return value, but no output schema exists and the update semantics are standard enough that this is not a serious gap.

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 baseline is 3. The description adds value by highlighting show_on_front, page_on_front, start_of_week, and timezone and explaining their real-world effects, which helps an agent reason about parameter impact beyond the schema's individual field descriptions.

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?

The description opens with a specific verb+object ('Update the site's core settings') and then pins the scope with concrete examples like show_on_front, page_on_front, start_of_week, and timezone. This clearly distinguishes it from sibling tools such as get_site_settings or update_plugin_settings without needing to inspect 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?

It clearly conveys when the tool is appropriate: for core global site settings rather than plugin, theme, or content settings. It also states a prerequisite (Administrator account). It does not explicitly name alternatives or exclusions, but the context is sufficient for an agent to route to this tool correctly.

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

Deploy Server

Other Tools