wp-mcp-control-server

wp_create_landing_page

Create structured landing pages with hero, services, testimonials, FAQ, and CTA sections. Set title, slug, and status to publish or draft.

Instructions

Create a landing page with structured sections (hero, services, testimonials, FAQ, CTA)

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": {
      "title": "<title>",
      "sections": "<sections>"
    },
    "name": "wp_create_landing_page"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	No
`title`	Yes	Page title
`status`	No		draft
`sections`	Yes	Page sections to compose

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 20, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only says 'create', implying a write operation, but fails to disclose important traits such as whether duplicates are checked, what happens on conflict, authentication needs, or side effects like modifications to other entities.

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?

The description is a single, clear sentence with no wasted words. It front-loads the core action ('Create a landing page') and lists the section types efficiently.

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?

Given the tool's complexity (4 parameters, nested array for sections, no output schema, no annotations), the description is too brief. It does not explain return values, error conditions, or how the sections parameter is used. More detail is needed for an agent to invoke it correctly without additional knowledge.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 50% (title and sections have descriptions, slug and status do not). The description does not add any parameter-level meaning beyond the schema, failing to clarify slug rules or status options. It does not compensate for the undocumented parameters.

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 clearly states the tool creates a landing page with specific structured sections (hero, services, testimonials, FAQ, CTA), which distinguishes it from generic page/post creation tools like wp_create_page and wp_create_post. The verb 'create' and resource 'landing page' are specific.

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 like wp_create_page. There is no mention of prerequisites, exclusions, or context that helps an agent decide.

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

Deploy Server