Skip to main content
Glama
Sign In
wordpress-mcp

wordpress-mcp

by cvrt-jh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

fulfillment_fulfill_order

Manually run fulfillment for a WooCommerce order: renders the packing slip, creates a ClickUp task, and notifies Slack. Bypasses the idempotency guard, so use with care.

Instructions

Manually (force) run fulfillment for an order: renders the packing slip, creates the ClickUp task, notifies Slack. Bypasses the idempotency guard, so it can create a duplicate ClickUp task. Audit-logged.

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": "<site>",
      "order_id": "<order_id>"
    },
    "name": "fulfillment_fulfill_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
order_idYesThe WooCommerce order id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.4.0

TDQS

A4.2/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses the idempotency guard bypass, the concrete risk (duplicate ClickUp task), the side effects (packing slip, task, Slack notification), and that actions are audit-logged. This is exactly the kind of consequence information an agent needs before a destructive re-run.

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?

Two tight sentences with the action and its consequences front-loaded; no filler, every clause earns its place.

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 mutation tool with no annotations and no output schema, the description covers behavior and risk thoroughly. It stops short of describing the return value or any permission prerequisite, which would fully close the gap.

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 description coverage is 100%; both 'site' and 'order_id' are documented in the schema, including a pointer to list_sites. The description adds no parameter-level detail, so the 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 (run fulfillment), the resource (an order), and enumerates the concrete effects (packing slip, ClickUp task, Slack). It is clearly differentiated from siblings like fulfillment_queue and fulfillment_reprint_job, which do not force a full re-run.

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?

'Manually (force)' implies the tool is for deliberate manual invocation rather than the normal automated path, but it never names an alternative (e.g. fulfillment_queue) or states when NOT to use it. Usage context is implied, not spelled out.

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