wordpress_set_twitter_cardsDefine Twitter Card meta tags for WordPress posts to control how content is displayed when shared on Twitter. Improve social sharing previews for any post ID.
Set Twitter Card meta tags for social sharing
| Name | Required | Description | Default |
|---|---|---|---|
| postId | Yes |
Changes observed during successful MCP inspections.
v1.0.0Input schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"Input schema / additionalPropertiesAdded value: +falseDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the burden of behavioral disclosure. It only states the action without revealing that it modifies existing post meta, requires authentication, or has any side effects. The description is too sparse to inform the agent about the operation's impact.
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 a single concise sentence with no unnecessary words, making it easy to parse. However, it is slightly under-specified, lacking important context that could have been added without excessive length.
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 simple schema but lack of annotations and output schema, the description is not complete enough. It does not explain what Twitter Card meta tags are, how postId is used, what values are set, or whether existing tags are overwritten. This lack of detail makes it difficult for an agent to fully understand the tool's scope.
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?
The input schema includes a required 'postId' of type 'number' with no description, and the description does not mention it. With 0% schema description coverage, the description should explain that postId identifies the target post, but it fails to do so, leaving the parameter ambiguous.
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 the tool's function with a specific verb ('Set') and resource ('Twitter Card meta tags'), and adds context ('for social sharing'). This distinguishes it from siblings like wordpress_set_og_tags and wordpress_set_seo_meta.
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 guidance is provided on when to use this tool versus alternatives such as wordpress_set_og_tags or wordpress_set_custom_meta. The description does not mention exclusions or specific scenarios where Twitter Cards are appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.