Skip to main content
Glama

create_post_with_embeds

Creates a WordPress post or page and embeds YouTube videos and social media URLs directly into its content, so you can build rich media posts without manual embed markup.

Instructions

Create WordPress post with embedded YouTube videos and social media content

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

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
tagsNoTag IDs (posts only)
titleYesPost title
statusNoPost status. Defaults to 'draft' so nothing is published unintentionally. 'future' is not available because this tool has no date parameter.draft
contentYesBase post content (embeds will be added)
post_typeNoPost type (post or page)
categoriesNoCategory IDs (posts only)
social_urlsNoSocial media URLs to embed (Twitter, Instagram, Facebook, TikTok)
youtube_urlsNoYouTube video URLs to embed

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world write. The description adds nothing beyond that: it doesn't say where embeds are inserted relative to content, whether existing content is altered, that status defaults to draft, or what permissions are needed. For a mutation tool with four embed-related parameters this is a real gap.

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 or redundancy. It is efficient, though the terseness leaves little room for the routing and behavioral information an agent needs.

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?

This is a nine-parameter write tool with no output schema, and the description covers only the embedding aspect. It says nothing about the post_type/status/categories/tags interplay, the default draft state, or what the call returns, leaving the agent to reconstruct the tool's behavior from the schema alone.

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 coverage is 100%, so every one of the nine parameters is already documented in the schema, which sets the baseline at 3. The description only gestures at the two embed parameters (youtube_urls, social_urls) and adds no syntax, ordering, or format detail beyond them.

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?

The description uses a specific verb+resource ('Create WordPress post') and adds the distinguishing feature of embedded YouTube and social media content, which separates it from plain create_post. It stops short of naming any sibling explicitly, so the differentiation is implied rather than stated.

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?

The mention of embeds implies the use case (call this when the post body must include YouTube or social media embeds), but there is no explicit when-to-use, when-not-to-use, or pointer to the alternative create_post/create_advanced_post tools. Guidance is inferable but not written.

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