Retrieve all categories for a specific NexusPress publication using its site slug to organize or select the right category when creating article drafts.
List categories for one NexusPress publication.
| Name | Required | Description | Default |
|---|---|---|---|
| siteSlug | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It implies a read via 'List' but does not state whether results are paginated, ordered, cached, or what happens if the publication has no categories. For a no-annotation tool this is a significant gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no filler. It is appropriately sized for a simple list operation, though the economy comes at the cost of detail rather than from dense information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With one required parameter, no annotations, and no output schema, the description should at minimum clarify the scope key (siteSlug) and basic return behavior. Neither is present, so it is thin for even a simple lookup tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0% for the single required parameter 'siteSlug'. The description mentions 'one NexusPress publication', which loosely hints at the scoping parameter, but never explains that siteSlug identifies the publication or what format it takes. The description does not compensate for the undocumented parameter.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('List') and resource ('categories') with an explicit scope ('for one NexusPress publication'). It is clear what the tool does, though it offers no differentiation from the six sibling tools (which concern publications, article drafts, and images) beyond the distinct resource name.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
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 tool versus alternatives, no prerequisites, and no exclusions. The agent must infer that this is a read-only lookup used when categories for a specific publication are needed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.