Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Get comment

wordpress_get_comment
Read-only

Retrieve a specific WordPress comment by ID to view its content, author, and moderation status. Use it to inspect individual comments for review or troubleshooting.

Instructions

[UNIFIED] Get a specific WordPress comment by ID. Returns complete comment data including content, author, and moderation status.

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_get_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
comment_idYes

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

B3/5.0
Behavior3/5

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

The readOnlyHint annotation already establishes this is a safe, non-mutating read, so the description is not required to carry the safety profile. It adds useful context about the payload ('complete comment data including content, author, and moderation status'), but says nothing about permissions, whether unpublished/spam comments are visible, or error behavior for invalid IDs.

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 short sentences with the core verb and resource front-loaded; the '[UNIFIED]' prefix is inert noise but everything else earns its place. Slightly more detail on the site parameter would have been a better use of the space.

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

Completeness3/5

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

For a simple two-parameter read tool with annotations and no output schema, the description is mostly adequate, but with 0% schema coverage the unexplained 'site' parameter leaves a real gap an agent must guess through.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate and it only partially does. 'By ID' maps loosely to comment_id, but the required 'site' parameter — presumably a site identifier or slug — is never mentioned, leaving the agent to infer its format and purpose.

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?

States a specific verb and resource ('Get a specific WordPress comment by ID') and names the returned data (content, author, moderation status), so the agent knows exactly what it retrieves. It does not, however, explicitly distinguish itself from sibling mutation tools such as wordpress_update_comment or wordpress_delete_comment.

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 call this versus alternatives such as wordpress_get_post (to list a post's comments) or the update/delete comment tools. The 'by ID' phrasing implies you already need a comment_id, but no prerequisites or exclusions are stated.

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