Skip to main content
Glama

create_post_with_featured_image

Create a WordPress post with a featured image by providing a title, content, and media ID; optionally set status and slug, with draft as the default.

Instructions

Create a new WordPress post with featured image

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": {
      "title": "<title>",
      "content": "<content>",
      "featured_media_id": "<featured_media_id>"
    },
    "name": "create_post_with_featured_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoURL slug (optional). If omitted, WordPress generates one from the title (a Japanese title gives a Japanese slug). Use it to set an ASCII slug, e.g. 'my-first-post'. WordPress may change it (for example, appending '-2' if the slug is already used); the result shows the actual slug
titleYesThe post title
statusNoPost status. Defaults to 'draft' so nothing is published unintentionally. 'future' is not available because this tool has no date parameter.draft
contentYesThe post content
featured_media_idYesMedia ID for featured image

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and non-idempotent, so the safety profile is covered. The description adds nothing beyond them: it does not say the post defaults to draft, that duplicate calls will create duplicate posts, that the media ID must already exist, or what permissions are required. With annotations present the bar is lower, but zero added behavioral context earns a 2.

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?

A single front-loaded sentence with no filler, but its brevity is achieved by omitting information rather than by compressing it; the definition is terse to the point of being skeletal for a write operation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The rich schema compensates for much of the gap, and annotations cover safety, so an agent can invoke it correctly. Still, for a non-idempotent creation tool with no output schema, the description should say what comes back (post ID, actual slug) and that the featured media must pre-exist.

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%, so every parameter including slug, status enum, and featured_media_id is already documented with nuance (WordPress slug rewriting, why 'future' is unavailable). The description adds no parameter meaning at all, which is the baseline 3 case.

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 ('Create'), resource ('WordPress post'), and a distinguishing attribute ('with featured image'), which separates it from the plain create_post sibling. It stops short of naming siblings explicitly, so an agent must infer that create_post_with_categories_tags or create_advanced_post cover the other variants.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the name: use this when a featured image must be attached at creation time. There is no explicit when-to-use statement, no when-not, and no named alternative for creating a post without an image or for adding an image to an existing post (set_featured_image).

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