Skip to main content
Glama
Sign In
mcp-wordpress

mcp-wordpress

by iamsamuelfraga
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wp_bulk_find_replace

Find and replace exact text within WordPress post content. Preview changes with a dry run, then apply using the returned confirmation token.

Instructions

Find and replace a literal substring across post content. Requires MODE=full. Dry-run by default (returns count + sample of changes). To apply, set dry_run=false and provide the confirm token returned by the dry-run. Operates on rendered post_content only; does not touch titles, excerpts, or meta.

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": {
      "find": "<find>",
      "replace": "<replace>"
    },
    "name": "wp_bulk_find_replace"
  }
}

Input Schema

NameRequiredDescriptionDefault
findYes
statusNopublish
confirmNo
dry_runNo
replaceYes
per_pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description fully discloses the safety workflow: dry-run default, confirm token required to apply, and the limitation to rendered post_content. This goes well beyond the schema to inform the agent about side effects and safeguards.

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?

The description is three sentences and front-loads the core purpose. The 'Requires MODE=full' clause is a minor distraction but does not undermine clarity.

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 no output schema and 6 parameters, the description covers the essential workflow and scope well. Missing details include parameter semantics for status/per_page and the MODE requirement, which leaves a small 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?

The description explains dry_run, confirm, and find/replace implicitly. However, with 0% schema description coverage, it leaves status, per_page, and the 'MODE=full' requirement unexplained, creating partial ambiguity.

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 opens with 'Find and replace a literal substring across post content,' using a specific verb and resource. It clearly differentiates from siblings by noting it operates on post_content only and does not affect titles/excerpts/meta.

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 explains the dry-run then confirm workflow, which is key to using the tool safely. It also clarifies scope by stating what it does not touch, but it does not explicitly name alternative tools or exclusion conditions.

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