Skip to main content
Glama
alokemajumder

wpxmcp

by alokemajumder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Create a comment

create_comment

Post comments on WordPress content, optionally as threaded replies. Set status to 'approve' to publish instantly or leave in moderation queue.

Instructions

Post a comment on a content item, optionally as a threaded reply. Set status to "approve" to publish it immediately (requires moderation capability); otherwise it enters the normal moderation queue.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoISO 8601 date to backdate the comment.
postYesContent ID to comment on. Its comment_status must be "open".
authorNoPost as this registered user ID.
parentNoComment ID this replies to, for threading.
statusNoModeration status. Requires moderate_comments to set.
contentYesThe comment body. Basic HTML is allowed; WordPress sanitises it.
site_idNoWhich configured WordPress site to act on. Optional — with a single site configured it is used automatically; with several, the default site is used unless you name one. Run list_sites for valid ids.
author_urlNoCommenter website URL.
author_nameNoDisplay name, when not commenting as a logged-in user.
author_emailNoEmail, when not commenting as a logged-in user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / author / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / author / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / parent / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / parent / minimum
      Added value: +-9007199254740991
    • addedInput schema / properties / post / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / post / minimum
      Added value: +-9007199254740991
  2. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations only indicate non-read-only and non-destructive; the description adds the moderation workflow (approve vs queue) and the permission requirement for approve. This goes beyond what annotations and schema already say, providing useful behavioral context.

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 sentences, front-loaded with the main action and threading option, then the moderation nuance. No redundant text.

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 creation tool with a well-documented schema, the description captures the essential purpose and the critical moderation behavior. It omits some prerequisites (comment_status must be open) but those are in the schema.

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 covers all parameters at 100%, so description adds limited extra meaning. It clarifies the effect of the status parameter ('approve' publishes immediately) which is a slight addition to the schema's description, but not substantial.

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 'Post a comment on a content item' with a specific verb and resource, plus the optional threading nuance. Clearly distinguishes from sibling tools like update_comment, delete_comment, and moderate_comments by focusing on creation.

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?

Implicitly indicates usage for creating comments, but does not explicitly mention when to use it vs alternatives like update_comment or moderate_comments. The moderation queue mention hints at post-creation behavior but not explicit routing.

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