Skip to main content
Glama

set_front_page

DestructiveIdempotent

Assign a static WordPress page as the site's front page by providing its page ID.

Instructions

Set a static page as the front page

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": {
      "page_id": "<page_id>"
    },
    "name": "set_front_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYesPage ID to set as front page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

Annotations already declare this is a non-read-only, idempotent, and apparently destructive mutation, but the description adds no behavioral context beyond that. It does not say that the currently configured front page is replaced/overwritten, nor whether the page must already exist or be published, which is exactly the kind of context a destructive hint begs for.

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?

A single short sentence with the action and target front-loaded and no filler. Nothing in it is wasted.

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 a one-parameter tool with full schema coverage and annotations covering the safety profile, the description is close to sufficient. The main missing piece is disclosure that the existing front page setting is replaced, which matters given destructiveHint=true.

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 coverage is 100%, with page_id already documented as 'Page ID to set as front page', so the schema carries the parameter burden. The description adds only the notion that the target must be a static page, which is marginal meaning beyond the schema.

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?

States a specific verb ('Set') and resource ('a static page as the front page'), which is a clear, unambiguous action. The word 'static' implicitly distinguishes it from the sibling set_front_page_to_posts, though it never names that sibling explicitly.

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?

The phrase 'static page' implies the alternate use case (a posts-based front page), so an agent can infer when this tool applies rather than its sibling. However, there is no explicit when-to-use statement, no mention of the sibling alternative, and no prerequisites such as the page needing to be published.

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