Skip to main content
Glama

Publish article

publish-article
Destructive

Publish an article. Auto-routes to a connected CMS integration when exactly one is connected for the article's domain. With several connected, target_provider picks one. With none, deployed_url records where the article was deployed by hand. The local status becomes "published" unless wp_status is draft; the publish date is set on the first publish and kept after that. A new WordPress post takes the article's slug. featured_image_url sets the WordPress featured image; if it cannot be used, the post still publishes and featuredImage says why. Confirm with the user first.

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": {
      "article_id": "<article_id>"
    },
    "name": "publish-article"
  }
}

Input Schema

NameRequiredDescriptionDefault
wp_statusNoWhen publishing to WordPress, whether the WP post should be live ("publish") or saved as a draft ("draft").publish
article_idYesArticle ID from list-articles
deployed_urlNoRequired when no CMS integration is connected. The public URL where the article was deployed manually.
target_providerNoRequired when multiple CMS integrations are connected for the article's domain.
featured_image_urlNoPublic https URL of a JPEG, PNG, WebP or GIF image (up to 10 MB) to upload to WordPress as the featured image. Ignored for a manual publish.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / article_id / description
      Previous value: -"Article ID"New value: +"Article ID from list-articles"
  2. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / article_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Changed1 schema field changed
    • addedInput schema / properties / featured_image_url
      Added value: +{
      +  "description": "Public https URL of a JPEG, PNG, WebP or GIF image (up to 10 MB) to upload to WordPress as the featured image. Ignored for a manual publish.",
      +  "format": "uri",
      +  "maxLength": 2048,
      +  "type": "string"
      +}
  4. First observed

TDQS

A4.7/5.0
Behavior5/5

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

The annotations already declare this as destructive and open-world, and the description adds substantial behavioral detail: auto-routing rules, local status changes, publish-date retention, WordPress slug behavior, and featured-image fallback behavior. This goes well beyond what the annotations provide.

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

Conciseness5/5

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

The description is front-loaded with the core action and then proceeds through routing, status, slug, image handling, and confirmation in a logical order. Despite covering several conditions, every sentence contributes useful information without repetition.

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?

The description covers the key invocation behavior and even notes a featuredImage failure detail, while annotations handle safety semantics. With no output schema, however, it does not describe the overall response shape or success return values, leaving a minor completeness gap.

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

Parameters5/5

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

Although schema description coverage is 100%, the description adds important cross-parameter semantics: target_provider is used when several CMS integrations exist, deployed_url applies when none exist, wp_status controls draft vs live status, and featured_image_url is ignored for manual publishes. These conditional relationships are not fully captured by the individual schema fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: "Publish an article." It further clarifies the action through CMS routing and manual-deployment behavior, making it distinguishable from siblings like update-article or archive-article even though none are named explicitly.

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 clearly explains the conditional usage of target_provider and deployed_url based on whether zero, one, or multiple CMS integrations are connected, and it adds an explicit prerequisite: "Confirm with the user first." It does not, however, state when to prefer this tool over update-article or archive-article, so it falls short of full when/when-not guidance.

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