Skip to main content
Glama
Sign In

Frontman for WordPress

by io.github.frontman-ai
OverviewDiscussionsAdmin

wp_read_widget

Read-onlyIdempotent

Reads a widget's current settings and sidebar placement.

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": {
      "site_id": "<site_id>",
      "widget_id": "<widget_id>"
    },
    "name": "wp_read_widget"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYesThe connected site's id returned by list_sites. Call list_sites first; do not use a URL or WordPress post ID.
widget_idYesThe widget instance ID (e.g. "text-2").

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so safety is covered. The description adds that both settings and sidebar placement are returned, which is useful behavioral context, but says nothing about failure modes or whether placement is null for inactive widgets.

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, hedging, or redundant restatement of the tool name. Nothing could be removed without losing information.

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?

Given full annotation coverage, two fully documented required parameters, and no output schema, the definition covers what an agent needs to invoke it correctly. It partially compensates for the absent output schema by naming the two categories of returned data, though it does not describe the response shape.

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 both parameters fully described, including the widget_id example format and the list_sites prerequisite, so the baseline is 3. The description contributes no additional parameter meaning beyond what the schema already states.

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 ('Reads') and resource ('widget's current settings and sidebar placement'), which is more specific than a bare 'get widget'. It does not name any sibling or explain how it differs from wp_list_widget_areas or wp_elementor_get_widget_schema, so differentiation is left to the reader.

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?

No explicit when-to-use, when-not-to-use, or alternatives are given; usage is only implied by the read-oriented framing (e.g. inspecting state before wp_update_widget or wp_move_widget). The prerequisite of calling list_sites first lives only in the schema, not the description.

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

All Frontman for WordPress toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources