Skip to main content
Glama
Sign In
wp-mcp-control-server

wp-mcp-control-server

by mpierre135
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wp_elementor_regenerate_css

Regenerate Elementor CSS assets for a WordPress page to reflect structural changes and fix outdated styling. Provide the page ID to rebuild its stylesheet and restore consistent design.

Instructions

Regenerate Elementor CSS assets for a page after structural changes

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

Input Schema

NameRequiredDescriptionDefault
page_idYesWordPress page ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.3.0

TDQS

A3.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state whether existing CSS is overwritten, whether the operation is safe to rerun, what side effects occur, or what success/failure looks like.

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 front-loaded sentence with no filler. The action, target, and trigger are all stated efficiently.

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, no-output-schema tool, the description is reasonably complete: it names the action, the affected resource, and the appropriate timing. It could add a note about safety or side effects, but it does not leave an agent guessing about what resource to pass or when to invoke it.

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 page_id is already described as 'WordPress page ID'. The description adds only a generic 'for a page' context, not new type, format, or constraints, so the baseline of 3 is appropriate.

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 uses a specific verb ('Regenerate') and identifies a precise resource ('Elementor CSS assets for a page'), plus the trigger context ('after structural changes'). No sibling tool covers CSS regeneration, so it is clearly distinguishable.

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

Usage Guidelines4/5

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

It gives a clear usage context by specifying when to call it ('after structural changes'), which helps an agent decide. It does not explicitly name alternatives or exclusions, but the sibling list does not contain an obvious competing CSS-regeneration tool.

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

Deploy Server

Other Tools