Skip to main content
Glama
Sign In
wordpress-mcp

wordpress-mcp

by cvrt-jh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

seo_delete_post_seo

Delete or reset the SEO meta for a WordPress post to remove outdated or incorrect SEO settings. Specify the site and post ID to clear them.

Instructions

Delete (reset) the SEO meta for a post.

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>",
      "id": "<id>"
    },
    "name": "seo_delete_post_seo"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPost ID
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.4.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It usefully signals that deletion means 'reset' rather than hard removal, but it omits whether the operation is reversible, what happens to default/fallback SEO values, permission requirements, and error behavior when no SEO meta exists.

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?

A single tight sentence with the key semantic clarification front-loaded; nothing redundant and nothing padded.

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 mutation tool with no annotations and no output schema, the description is too thin: it does not cover return behavior, permission needs, or interaction with the corresponding get/update tools. The '(reset)' hint is helpful but insufficient.

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 100% (id = Post ID, site = Site id referencing list_sites), so the schema already documents both parameters. The description adds no additional meaning beyond that, which is the expected baseline.

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 (Delete) and resource (SEO meta for a post), and the parenthetical '(reset)' clarifies the semantics of the delete. It is distinguishable from seo_delete_term_seo via 'for a post', but it does not explicitly contrast with siblings like seo_update_post_seo or seo_get_post_seo.

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?

No guidance on when to use this versus seo_update_post_seo (clearing fields), seo_bulk_update_posts_seo, or seo_delete_term_seo, and no preconditions stated. The agent must infer usage entirely from the name.

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