Skip to main content
Glama

set_front_page_to_posts

DestructiveIdempotent

Configure WordPress to show the latest posts on the front page instead of a static page, with an optional page ID for the blog posts page.

Instructions

Set front page to show latest posts

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

Input Schema

NameRequiredDescriptionDefault
posts_page_idNoOptional page ID to use for blog posts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is partially covered. The description adds nothing about what is overwritten — e.g. that it replaces the existing front page configuration site-wide — or whether the previous setting is recoverable, which matters for a destructive 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?

A single front-loaded sentence with no wasted words. It is terse rather than bloated, though that brevity comes at the cost of the missing behavioral detail.

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?

For a destructive, site-wide settings mutation with no output schema, the description should disclose side effects and the role of posts_page_id. Neither is present, leaving the agent dependent entirely on annotations and the schema.

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% and the single optional posts_page_id is documented there, so baseline 3 applies. The description never mentions the parameter or how supplying a posts page differs from omitting 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 gives a specific verb and resource ('set front page') plus the target state ('show latest posts'), which is unambiguous on its own. It does not, however, distinguish this from the sibling set_front_page, which plausibly configures a static front page instead.

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 guidance on when to use this versus set_front_page or any other sibling, and no stated prerequisites or exclusions. An agent must infer the choice from tool names alone.

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