Skip to main content
Glama

Create blog content

create_content

Create a post or page on the connected blog. The default is an unpublished draft. Set content.publish to true only when the user explicitly asks to publish publicly and the connection has publishing consent. Use html for simple content or ordered native elements. Returns preview_url and preview_expires_at; anyone with the link can read the draft for 30 minutes.

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": {
      "kind": "<kind>",
      "content": "<content>"
    },
    "name": "create_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
contentYes
idempotency_keyNoReuse the same key only when retrying the exact same creation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false), the description discloses the draft-by-default state, the publishing-consent gate, and the security-relevant fact that the returned preview link is publicly readable for 30 minutes. It omits retry/idempotency behavior and any failure modes, which would round it out.

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?

Five short sentences, front-loaded with the verb and the safe default, then the risky publish condition, then the encoding choice and return values. Minor redundancy in restating the publish rule already present in the schema description, but the ordering is deliberate and efficient.

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

Completeness4/5

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

For a creation tool with a rich nested payload and no output schema, the description covers the essentials: default draft state, consent required for publication, content representation choice, and both returned fields including their expiry. Missing idempotency/retry semantics and error behavior keep it from being complete.

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?

With only 33% schema description coverage on a deeply nested object, the description adds little parameter-level meaning: it clarifies the html-vs-elements choice and reinforces the publishing gate on content.publish, both of which the schema already states. It says nothing about slug rules, tag/author IDs, or the idempotency_key retry contract, which is significant given idempotentHint=false.

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 and resource ('Create a post or page on the connected blog') and uses the required 'kind' enum to disambiguate posts from pages. It does not distinguish itself from siblings such as update_content or publish_content, so an agent must infer whether publishing belongs here or in the dedicated publish tool.

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

Usage Guidelines4/5

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

Gives concrete when-to guidance: the default is an unpublished draft, and content.publish should be true only when the user explicitly requests public publication and consent exists. The gap is that it never acknowledges the sibling publish_content/unpublish_content tools, leaving a real ambiguity about whether to publish in this call or a follow-up one.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources