Skip to main content
Glama
Sign In

Howseen

by ai.howseen
OverviewDiscussionsAdmin

Publish an article

publish_article
Destructive

Publish a written article (e.g. a draft from draft_article) to the brand's connected CMS (WordPress, Shopify, Ghost, BigCommerce, GoHighLevel, Webflow, webhook) or hosted blog, now, or schedule it for a later date (needs Autopilot ON). Goes live publicly. Preview first; confirm: true publishes and returns the URL.

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
brandNoBrand id, name or domain (from list_brands). Optional when the account has a single brand.
confirmNoLeave out (or false) to get a preview: nothing changes. Set true ONLY after the user approved that exact preview.
platformNoOptional: wordpress, shopify, ghost, bigcommerce, webhook, nextjs (hosted blog / Next.js feed) or api. Default: the CMS Autopilot uses (most recently connected).
article_idYesArticle id from list_articles or get_article_performance.
publish_atNoOptional YYYY-MM-DD after today to schedule instead of publishing now (Autopilot must be ON).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, so the bar is lower. The description adds meaningful context beyond them: 'Goes live publicly' clarifies real-world impact, and the preview/confirm mechanism explains how to safely invoke a destructive action. It doesn't cover auth or rate limits, so not a 5.

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 leads with the verb and resource, then packs in the preview flow and scheduling constraint. It is dense with parentheticals but every clause earns its place; slightly dense formatting keeps it from a 5.

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?

With no output schema, the description usefully notes that publishing returns the URL. Combined with 100% parameter coverage and the preview/confirm and Autopilot constraints, an agent has what it needs to invoke correctly, though return detail is minimal.

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

Parameters4/5

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

Schema coverage is 100%, giving a baseline of 3. The description reinforces the critical 'confirm: true publishes and returns the URL' semantics and implies the platform scope, adding marginal value on the highest-stakes parameter beyond the schema.

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 states a specific verb (publish) and resource (a written article), enumerates the destination CMS platforms, and distinguishes it from the sibling draft_article by referencing 'a draft from draft_article'. An agent can tell exactly what this does versus drafting.

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 provides a clear workflow: 'Preview first; confirm: true publishes and returns the URL,' and notes scheduling 'needs Autopilot ON.' It routes back to draft_article for draft creation implicitly but does not explicitly state when not to use this or name a direct alternative path in full.

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

All Howseen toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources