Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Update comment

wordpress_update_comment
Destructive

Update an existing WordPress comment's content, status, author name, or email by specifying the site and comment ID.

Instructions

[UNIFIED] Update an existing WordPress comment. Can update content, status, author information, etc.

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>",
      "comment_id": "<comment_id>"
    },
    "name": "wordpress_update_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
statusNo
contentNo
comment_idYes
author_nameNo
author_emailNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.13.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv3.4.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and non-idempotent, so the safety profile is covered. Beyond that the description adds nothing behavioral: it does not say whether omitted/null optional fields leave values untouched, whether updates overwrite, or whether the response confirms the new state — significant gaps for a destructive mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the operation, with no filler sentences. However, the "[UNIFIED]" tag and "etc." waste the limited space and introduce vagueness rather than precision.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter destructive mutation with zero schema description coverage and no output schema, the definition is thin. It omits null/omission semantics, valid status values, and any confirmation of return behavior, leaving the agent to guess at the most consequential details.

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 0%, so the description should compensate. It names content, status and author information, which maps to four of the six parameters, but leaves site and comment_id unexplained and never clarifies that null defaults mean "no change" or what values status accepts (no enum exists).

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?

"Update an existing WordPress comment" is a specific verb+resource pair, and the mention of content, status and author information scopes the operation. It is clearly distinct from the create/delete/get comment siblings by name and verb, though it never explicitly names them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this versus wordpress_create_comment, delete_comment, or bulk_update alternatives, and no preconditions (e.g., permissions, whether the comment must exist). The trailing "etc." actively weakens what little scope is given.

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