Skip to main content
Glama
Sign In

Frontman for WordPress

by io.github.frontman-ai
OverviewDiscussionsAdmin

wc_maint_clear_sessions

Destructive

Delete all customer sessions, including current and saved carts, and flush the object cache. Ask the user for confirmation before calling with confirm=true.

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>",
      "confirm": "<confirm>"
    },
    "name": "wc_maint_clear_sessions"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be true only after explicit user confirmation.
site_idYesThe connected site's id returned by list_sites. Call list_sites first; do not use a URL or WordPress post ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, but the description adds the information the annotation cannot convey: exactly which data is destroyed (all customer sessions, current carts, saved carts) plus an additional side effect (object cache flush). It also states the human-in-the-loop gate, which is critical for an irreversible bulk delete.

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?

Two sentences with no filler; the destructive scope is front-loaded and the safety instruction follows. Slightly more could be trimmed, but every clause carries real 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?

For an irreversible bulk-delete tool with no output schema, the description covers what is destroyed, the cache side effect, and the confirmation requirement. It stops short of saying how the operation is scoped relative to site_id (all sites vs the given site) or what the result reports back.

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 both parameters document themselves, including the confirm=true precondition and the site_id sourcing from list_sites. The description only restates the confirm semantics already in the schema and adds nothing about site_id, so baseline 3 applies.

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?

States a specific verb and resource ('Delete all customer sessions') plus the exact scope of collateral damage ('including current and saved carts') and a secondary action ('flush the object cache'). That is far more specific than the sibling maintenance tools, which only clear transients, caches, or lookup tables.

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?

Gives a clear procedural condition: ask the user for confirmation before calling with confirm=true. It does not compare itself against plausible alternatives such as wp_clear_cache or wc_maint_clear_transients, so there is no explicit when-to-use-this-vs-that routing, but the destructive precondition is unambiguous.

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