Skip to main content
Glama

wordpress_create_post

wordpress_create_post

Create a WordPress post by specifying title and content, with full control over all post properties.

Instructions

Create a new WordPress post with full control over all post properties

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
contentYes
Behavior2/5

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

No annotations provided; description fails to disclose default post status (draft vs published), required capabilities, or side effects. Vague 'create' without behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is efficient, but the phrase 'full control over all post properties' is inaccurate given schema constraints, slightly undermining conciseness.

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 no output schema and no behavioral details, description is insufficient for a create tool. Agent lacks knowledge of expected output, required permissions, or default behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage for parameters; description adds no semantic detail beyond parameter names. Claim of 'full control' misrepresents limited schema (only title and content).

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?

Describes creating a WordPress post, distinguishing from siblings like wordpress_create_page. However, claim of 'full control over all post properties' is misleading given only title and content are in schema.

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 tool versus alternatives like wordpress_bulk_create_posts, wordpress_publish_post, or wordpress_update_post. Agent has no context for selection.

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/RaheesAhmed/wordpress-mcp-server'

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