Skip to main content
Glama
Hermoso

Hermoso

Official

Publish a Webflow blog post

post_to_webflow
Destructive

Publish or draft a blog post in a Webflow CMS collection by mapping title, body, summary, cover image, and required fields; get the live item URL or a clear refusal for missing values.

Instructions

Use this when the user wants to publish or draft a BLOG POST on their Webflow site. It becomes an item in the site's blog CMS collection. Publishing costs no credits. A title is REQUIRED and the text becomes the body: plain text or light markdown becomes HTML in the collection's rich text field, and HTML is sent as written (Webflow's API cannot take code blocks, so a body with one is refused). Hermoso maps the post onto the collection's OWN fields: title and slug, the body, a summary field, a cover image field (up to 4 MB), and search title and description fields when the collection has them. A part the collection has no field for is refused by name, never dropped. REQUIRED FIELDS of the collection are filled from the post where they can be: a required Title or Headline field takes the title, an Intro or Summary field the excerpt (else the first lines of the body), every required image field the cover image. A required Author, Category or other choice is NEVER guessed: the refusal names each such field's slug, type and allowed values (a Reference's items by name and id, an Option's options), and you pass them in fieldData by slug; a Reference or Option value may be the item's or option's id or its name. fieldData also sets any other field. status: publish (default) or draft. Webflow's API CANNOT SCHEDULE a post: for a later time use schedule_post with the webflow channel. The reply is Webflow's own copy of the item, with its public address. Webflow has no view counts on an item: never quote one. Not connected: the user connects it under Connectors > Webflow, or you call connect_connector with provider webflow (token).

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_webflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
hookNothe post's angle — a list_hooks id or your own wording, reused exactly
slugNothe end of the post URL (made from the title when omitted)
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
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
subjectNowhat the post is about
imageUrlNoone image: becomes the cover (featured) image
seoTitleNo
videoUrlNoa link to a hosted video (YouTube or Vimeo), for a collection with a Video field; never a video file
fieldDataNothe collection’s own fields by slug, e.g. {author: "<item id or name>", category: "<option id or name>"} (list_webflow_collections with collectionId shows them and their allowed values)
imageUrlsNoseveral images: the first is the cover, the rest go inside the body
collectionIdNoa collection other than the one chosen for the blog
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
seoDescriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.571

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: publishing costs no credits, HTML is sent verbatim while code blocks are refused, unmapped parts are refused by name rather than dropped, required choice fields are never guessed and the refusal enumerates slug/type/allowed values, and the reply is Webflow's own item copy with its public address. It also warns that view counts do not exist on an item, which prevents a plausible hallucination.

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?

Front-loaded with the trigger and the scheduling exclusion, then organized by concern (body handling, field mapping, required fields, status, connection). It is dense and long, and a few clauses about field mapping could be tightened, but nearly every sentence carries operational information.

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?

For a 20-parameter mutation tool with no output schema, the description covers the return value ('Webflow's own copy of the item, with its public address'), the failure modes (refusals by field name, code blocks, duplicate posts), and the auth prerequisite. Nothing an agent needs to invoke it correctly is missing.

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 already 90%, yet the description still adds real meaning: text becomes the rich text body, imageUrl becomes the cover while imageUrls' first is the cover and the rest go inline, fieldData is keyed by collection slug with id-or-name values, and status defaults to publish. It does not explain every one of the 20 parameters (e.g. hook, recipe, ideaId are left to the schema), so it falls short of a 5.

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 or draft a BLOG POST on their Webflow site') and immediately clarifies the resulting object ('an item in the site's blog CMS collection'). It also distinguishes itself from the closest sibling by naming schedule_post for later times, so an agent can route correctly without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ('when the user wants to publish or draft a BLOG POST'), an explicit exclusion with the alternative ('Webflow's API CANNOT SCHEDULE a post: for a later time use schedule_post with the webflow channel'), and a prerequisite path for the unconnected case (Connectors > Webflow or connect_connector with provider webflow).

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