Skip to main content
Glama

update_settings

DestructiveIdempotent

Configure WordPress site settings including title, tagline, language, timezone, front page display, and posts per page to adjust how the site appears and behaves.

Instructions

Update WordPress site settings

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": "update_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoSite title
languageNoSite language code (e.g., 'ja', 'en_US')
timezoneNoSite timezone (e.g., 'Asia/Tokyo')
descriptionNoSite tagline/description
page_on_frontNoStatic front page ID (when show_on_front is 'page')
show_on_frontNoWhat to show on front page
page_for_postsNoPosts page ID (when show_on_front is 'page')
posts_per_pageNoNumber of posts per page
default_categoryNoDefault category for new posts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

Annotations already disclose destructiveHint=true and idempotentHint=true, so the safety profile is covered, but the description adds nothing beyond them: it does not say that all fields are optional and omitted ones are left untouched, nor what destructive means here (which settings can be reset or lost). For a write tool against site-wide configuration, this is a meaningful gap.

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?

A single front-loaded sentence with zero filler, so it is maximally concise, though the brevity is under-specification rather than density of useful information.

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

Completeness2/5

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

Nine optional parameters, a destructive write, and no output schema make this a case where the description should explain partial-update semantics, side effects on front-page/page-for-posts relationships, and required capability. It supplies none of that, so an agent can only call it correctly by reading the schema closely.

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%, including per-parameter descriptions and an enum for show_on_front, so the schema carries the full parameter burden and baseline is 3. The description adds no extra meaning such as the dependency between show_on_front and page_on_front/page_for_posts or accepted timezone/language formats.

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

Purpose3/5

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

The description states a specific verb and resource ('Update WordPress site settings'), which is clearer than a bare tautology, but it offers no differentiation from siblings that touch the same surface, notably set_front_page / set_front_page_to_posts (which overlap with the page_on_front/show_on_front parameters) and get_settings, the read counterpart.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites or permissions, and no pointer to alternatives such as set_front_page for front-page configuration or get_settings for reading current values. The agent must infer usage purely from the tool name.

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