Skip to main content
Glama
c-sakel
by c-sakel

Yoast SEO Meta aktualisieren

seo_update_yoast_meta

Update Yoast SEO meta data for WordPress posts and pages, including SEO title, meta description, focus keyword, canonical URL, Open Graph, Twitter, and noindex/nofollow settings.

Instructions

Aktualisiert Yoast SEO Meta-Daten eines Posts

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoSEO Titel
postIdYesPost/Page ID
noIndexNoNoIndex setzen
ogImageNoOpen Graph Image URL
ogTitleNoOpen Graph Titel
noFollowNoNoFollow setzen
descriptionNoMeta Description
canonicalUrlNoCanonical URL
focusKeywordNoFocus Keyword
twitterTitleNoTwitter Titel
ogDescriptionNoOpen Graph Description
twitterDescriptionNoTwitter Description
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It simply says 'updates' which implies mutation but lacks detail on overwriting behavior, permissions required, or return values. No potential side effects or limitations are disclosed.

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?

The description is a single, concise sentence with no redundant words. It is front-loaded and easy to parse. However, it is so brief that it borders on under-specification, though this is more of a completeness issue.

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?

Given the tool's complexity (12 parameters, no annotations, no output schema), the description is too sparse. It fails to mention that only provided fields are updated, that the Yoast plugin must be active, or what the tool returns. This leaves the agent without crucial operational context.

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?

The input schema has 100% description coverage, with each of the 12 parameters documented. The description itself adds no parameter information, but the baseline of 3 is appropriate since the schema already provides the necessary semantics.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Aktualisiert' (updates) and the specific resource 'Yoast SEO Meta-Daten eines Posts' (Yoast SEO meta-data of a post). This differentiates it from sibling tools like seo_update_rankmath_meta and seo_get_post_meta.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention compatibility requirements, when to avoid it, or contrast with seo_update_rankmath_meta. The only hint is the name, which is insufficient.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/c-sakel/wp-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server