Skip to main content
Glama
Sign In
Nucleo for WordPress

Nucleo for WordPress

by nucleowp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

nucleo-doc-texts

Read-onlyIdempotent

Retrieve every translatable text in a WordPress document as node ID, field path, and text, plus the revision required to update translations without touching layout structure.

Instructions

All translatable texts of a document, as node id, field path and text, without structure. Also returns the revision to pass to nucleo/doc-texts-set.

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": {
      "postId": "<postId>"
    },
    "name": "nucleo-doc-texts"
  }
}

Input Schema

NameRequiredDescriptionDefault
postIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description adds real value by disclosing the flat, structure-less return shape and by explaining that a revision token is returned for optimistic concurrency on the setter. That concurrency detail is behavior an agent could not infer from annotations or schema.

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 short sentences with no filler; the primary output description is front-loaded and the downstream hand-off is a single appended clause. Every sentence earns its place.

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?

Because there is no output schema, the description correctly takes on the job of describing the return fields and the revision token, which it does well. It leaves the sole input parameter undocumented and says nothing about behavior for invalid or nonexistent document ids.

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?

The schema has 0% description coverage, so the description carries the full burden for postId, but it never names or explains the parameter. An agent must infer from 'of a document' that postId is the document identifier, with no hint about valid ranges or what happens for a nonexistent id.

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?

The description states a specific resource and scope: 'All translatable texts of a document,' plus the exact shape returned (node id, field path, text). The mention of nucleo/doc-texts-set implicitly separates it as the read counterpart to the setter, though it never states the verb 'list' explicitly.

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?

The reference to passing the returned revision to nucleo/doc-texts-set implies a read-then-write workflow, which is useful context. However, there is no explicit statement of when to prefer this over nucleo-doc-get or nucleo-content-get, nor any exclusion guidance.

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