Skip to main content
Glama

Publish content

publish_content
Destructive

Publish the current draft to the public blog. Call only when the user explicitly asks to publish. Supply publication_date to preserve an original date when importing; past dates publish immediately and future dates schedule publication.

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>",
      "id": "<id>",
      "revision": "<revision>"
    },
    "name": "publish_content"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesContent ID returned by get_content or list_content.
kindYes
revisionYesExact quoted revision returned by get_content. Required to protect concurrent edits.
idempotency_keyNo
publication_dateNoOptional YYYY-MM-DDTHH:mm in the blog timezone from get_blog. A past date publishes immediately with that date. Empty string publishes now. Omit to retain the existing date or schedule.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / publication_date
      Added value: +{
      +  "description": "Optional YYYY-MM-DDTHH:mm in the blog timezone from get_blog. A past date publishes immediately with that date. Empty string publishes now. Omit to retain the existing date or schedule.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, and openWorldHint=true. The description adds real context beyond that: publishing makes the draft public, past publication_date values publish immediately while future ones schedule, and revision guards against concurrent edits. It still doesn't say what happens to the previously published version or that retries without an idempotency_key could duplicate a publish.

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?

Three short sentences, front-loaded with the action and then the guardrail and date semantics. No padding, though the publication_date sentence lightly restates the schema's own description.

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

Completeness5/5

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

No output schema exists, so the description must carry the behavioral load for a destructive, non-idempotent, publicly visible mutation; it does so with the explicit-request requirement and the full date-semantics matrix. The one genuine gap is idempotency_key, which is undocumented in both schema and description, leaving some residual ambiguity for retry behavior.

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 60%. The description usefully reinforces the publication_date branches (preserve original date, past = immediate, future = scheduled) and the concurrency reason for revision. However, it says nothing about kind (posts vs pages) and nothing about idempotency_key, which is empty in the schema and therefore documented nowhere.

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 gives a specific verb and resource: publishing the current draft to the public blog. It is clearly distinct from unpublish_content and get_content, though the title-heavy sibling publish_design is not addressed. An agent can identify the operation without opening the schema.

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?

It states an explicit precondition (call only when the user explicitly asks to publish), which is meaningful usage gating for a destructive operation. It does not name alternatives such as update_content (which keeps a draft unpublished) or unpublish_content, so the routing guidance is clear but incomplete.

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