Skip to main content
Glama
Hermoso

Hermoso

Official

Publish a Wix blog post

post_to_wix
Destructive

Publish, draft, or schedule a Wix blog post using a required title and body text; converts markdown or HTML into Wix rich content and adds images, tags, and categories.

Instructions

Use this when the user wants to publish, draft or schedule a BLOG POST on their Wix site. Publishing costs no credits. A title is REQUIRED (up to 200 characters) and the text becomes the body: plain text or light markdown is turned into Wix's own rich content, and HTML is converted by Wix (up to 30,000 characters). status: publish (default), draft, or scheduled with a future date, which Wix schedules natively. The FIRST image becomes the cover; other images and a video are brought into the site's Media Manager and placed in the body. tags and categories take names; one the blog lacks is CREATED, and the reply says which categories. A title over 200 characters, an excerpt over 500, a slug over 100 or more than 30 tags is refused, never cut. The reply is Wix's own copy of the post, with its public address once it is live. Not connected: the user connects it under Connectors > Wix, or you call connect_connector with provider wix (apiKey, siteId).

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": {
      "title": "<title>"
    },
    "name": "post_to_wix"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoISO time to publish at; a future date schedules it on Wix itself
hookNothe post's angle — a list_hooks id or your own wording, reused exactly
slugNothe end of the post URL, up to 100 characters
tagsNoup to 30 tags, by name
textNothe body: plain text, light markdown or HTML
brandNoWHICH PROFILE this post belongs to — id or exact name from list_brands (a shared workspace: its profile id). Beats the connection's pin for THIS CALL ONLY; a name that matches no profile, or two, is REFUSED and nothing is posted.
titleYesREQUIRED: the post title, up to 200 characters
ideaIdNoshort id of the content-plan idea this post came from
recipeNothe post's FORMAT id, e.g. "slideshow" or "imessage_chat" — post_performance groups by it, so reuse one id per format
statusNodefault publish
altTextNoalt text for the images
excerptNothe summary, up to 500 characters
subjectNowhat the post is about
imageUrlNoone image: becomes the cover (featured) image
memberIdNothe site member the post belongs to (default: the author of the site’s latest post)
seoTitleNothe search title
videoUrlNoone video, placed in the body
imageUrlsNoseveral images: the first is the cover, the rest go inside the body
categoriesNoup to 10 categories, by name
allowDuplicateNopost it even though an identical post was just made
idempotencyKeyNoany stable string: a repeat within 24h returns the original post instead of posting again
seoDescriptionNothe search description

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.571

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true and idempotentHint=false, so the safety profile is covered. The description still adds real value beyond that: no credit cost, HTML/markdown conversion by Wix, first image becoming the cover, missing tags/categories being CREATED, and hard refusals rather than truncation at the size limits. It does not mention the idempotencyKey retry behavior, which is the one behavioral trait an agent would want spelled out for a non-idempotent write.

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?

Front-loaded with the when-to-use clause, then requirements, then conversion behavior, then limits, then the return value, then the connection fallback. Dense but every sentence carries a distinct fact; nothing is repeated from the schema verbatim.

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 22-parameter write tool with no output schema, the description covers the essentials: required title, body handling, scheduling, media placement, limit refusals, and what the reply contains including the public address. The gap is that roughly a third of the parameters (brand, recipe, hook, ideaId, memberId, allowDuplicate, idempotencyKey) get no narrative treatment, though the schema documents them fully.

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%, so the baseline is 3, but the description adds meaning on top: title cap of 200, text treated as body with markdown/HTML conversion up to 30,000 characters, status default of publish, future date scheduling natively on Wix, and tags/categories taken by name with auto-creation. Several parameters (hook, recipe, brand, memberId, allowDuplicate, idempotencyKey) are left entirely to 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?

States a specific verb and resource ('publish, draft or schedule a BLOG POST on their Wix site'), which cleanly separates it from post_to_wordpress, post_to_shopify_blog and the other post_to_* siblings. The title reinforces the same scope.

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 triggering condition ('Use this when the user wants to publish, draft or schedule a BLOG POST on their Wix site') and names the fallback path when the connector is missing (Connectors > Wix, or connect_connector with provider wix). It does not explicitly contrast with the other blog-publishing siblings, but the Wix scoping makes the choice unambiguous.

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

Deploy Server

Other Tools