Skip to main content
Glama

Publish an article to a connected site

publish_article
DestructiveIdempotent

Publish (or save as draft) a previously generated article to its site: WordPress, or a Webflow/Framer site connected with an API token or key (Framer publishing deploys the whole project, so unpublished changes in the project go live too). Sites connected for copy-paste only are not supported here.

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": {
      "articleId": "<articleId>",
      "siteId": "<siteId>"
    },
    "name": "publish_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYesThe site id to publish to (WordPress, or a connected Webflow/Framer site)
statusNopublish
articleIdYesThe article id, from generate_article or list_articles

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / siteId / description
      Previous value: -"The WordPress site id to publish to"New value: +"The site id to publish to (WordPress, or a connected Webflow/Framer site)"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Goes beyond the annotations with a meaningful side-effect warning: Framer publishing deploys the entire project, so unrelated unpublished changes also go live. That is exactly the kind of context destructiveHint=true alone cannot convey. It still omits auth/permission requirements and failure behavior.

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 that names the action and supported platforms before the caveats. The nested parentheticals make it dense on first read, but no clause is filler.

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 destructive write tool with no output schema, the description covers the platform scope, the draft alternative, and the most consequential side effect. Missing details are secondary: confirmation/rollback behavior and what the response returns on success or partial deploy.

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 67%: siteId and articleId are documented in the schema, while status has only an enum and default. The description's '(or save as draft)' partially compensates by indicating what the status parameter selects, but adds no further syntax or defaulting guidance. Baseline 3 is appropriate.

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 (publish) and resource (a previously generated article) plus the destination (a connected WordPress/Webflow/Framer site), and clarifies the draft variant inline. It does not name a sibling to contrast with (e.g. schedule_article), so an agent must infer the boundary between immediate publishing and scheduling.

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 a clear usage context ('a previously generated article', 'connected with an API token or key') and an explicit exclusion: copy-paste-only sites are not supported here. It stops short of stating when to prefer this over schedule_article or cancel_scheduled_article.

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