AutoWP MCP Server

update-site-settings

Update basic WordPress site settings such as title, tagline, timezone, and front page. Modify site options directly through the REST API.

Instructions

Update basic 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-site-settings"
  }
}

Input Schema

Name	Required	Description
`title`	No	Site title
`language`	No	WordPress locale code
`siteIcon`	No	Media ID for the site icon
`siteLogo`	No	Media ID for the site logo
`timezone`	No	Timezone string, for example 'Africa/Nairobi'
`useSmilies`	No	Convert emoticons to graphics
`description`	No	Site tagline
`pageOnFront`	No	Page ID to use as the front page
`showOnFront`	No	What to show on the front page
`pageForPosts`	No	Page ID to use for posts page
`postsPerPage`	No	Number of posts shown per page
`defaultCategory`	No	Default post category ID
`defaultPingStatus`	No	Default pingback/trackback status
`defaultPostFormat`	No	Default post format
`defaultCommentStatus`	No	Default comment status

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 31, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It doesn't disclose whether changes are reversible, require specific permissions, or how partial updates behave. Only states the tool updates settings, leaving mutation behavior opaque.

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 sentence with no redundant words. It is front-loaded but the qualifier 'basic' adds little value and might mislead about scope.

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?

With 15 parameters, no annotations, and no output schema, this description is insufficiently complete. It doesn't explain return values, patch semantics, or the distinction between fields that affect live site behavior. For a complex mutation tool, more context is needed.

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 baseline is 3. The description adds no parameter-specific meaning beyond the schema, which already documents all 15 parameters with clear descriptions.

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 clearly states the tool updates WordPress site settings, using a specific verb and resource. It distinguishes itself from the read-only get-site-settings sibling. However, it doesn't enumerate which settings, though the schema provides that.

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?

No guidance on when to use this tool versus alternatives. The description doesn't mention prerequisites, exclusions, or scenarios where another tool would be appropriate. Usage is implied only by the verb 'Update'.

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