wordpress_delete_term
wordpress_delete_termDelete a term from a taxonomy by providing the taxonomy, term ID, and force flag.
Instructions
Delete a term from a taxonomy
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| taxonomy | Yes | ||
| termId | Yes | ||
| force | Yes |
wordpress_delete_termDelete a term from a taxonomy by providing the taxonomy, term ID, and force flag.
Delete a term from a taxonomy
| Name | Required | Description | Default |
|---|---|---|---|
| taxonomy | Yes | ||
| termId | Yes | ||
| force | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description bears full burden for behavioral disclosure. The brief statement 'Delete a term' does not explain the meaning of the `force` parameter, whether deletion is permanent, or what happens when a term is in use. This leaves significant gaps for an AI agent.
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?
The description is extremely short—one sentence. While concise, it omits critical details, making it under-specified rather than efficiently informative. It does not front-load essential usage 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?
Given the lack of annotations, output schema, and parameter descriptions, the description is incomplete. It does not cover important aspects like what the `force` parameter does, error conditions, or return values. For a simple 3-parameter tool, it still fails to provide sufficient context.
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%, meaning no parameter descriptions exist in the schema. The tool description adds no information about the parameters (taxonomy, termId, force). An agent has to rely solely on parameter names, which is insufficient for correct invocation.
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 clearly states 'Delete a term from a taxonomy', which is a specific verb and resource. It distinguishes from sibling tools like create_term, update_term, or get_terms. However, it lacks any additional context that could enhance clarity.
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?
No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives (e.g., wordpress_delete_category, wordpress_delete_tag), nor does it mention any prerequisites or consequences.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/RaheesAhmed/wordpress-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server