Skip to main content
Glama
Hermoso

Hermoso

Official

Publish a Shopify blog article

post_to_shopify_blog
Destructive

Publish, draft, or schedule articles on a Shopify store blog using a required title and text, converting light markdown to HTML and setting the first image as the featured cover.

Instructions

Use this when the user wants to publish, draft or schedule a BLOG ARTICLE on their Shopify store's blog. Publishing costs no credits. Works for an account created by installing Hermoso from the Shopify App Store (there is no Shopify tile to connect). A title is REQUIRED and the text becomes the body: plain text or light markdown (## headings, - lists, bold, links) becomes HTML, and HTML is sent as written. status: publish (default), draft, or scheduled with a future date, which Shopify schedules natively. The FIRST image becomes the featured image (Shopify copies it into the store); other images and a video go inside the body by their own links. A store with one blog needs no blog named; with several, pass blog (list_shopify_blogs); newBlogTitle creates a blog with the article. The reply is Shopify's own copy of the article, with its public address once published. An over-long tag is refused, never cut. A store that installed Hermoso before blog posts existed is asked to open the app once and approve the new permission. Shopify has no view counts on a blog article: never quote one.

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

Input Schema

NameRequiredDescriptionDefault
blogNowhich blog: title, handle or id (not needed when the store has one)
dateNoISO time to publish at; a future date schedules it on Shopify itself
hookNothe post's angle — a list_hooks id or your own wording, reused exactly
slugNothe end of the article URL (its handle)
tagsNotags, 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 article title
authorNothe byline (default: the store name)
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 shown in lists
subjectNowhat the post is about
imageUrlNoone image: becomes the cover (featured) image
seoTitleNothe search title
videoUrlNoone video, embedded in the body by its link
imageUrlsNoseveral images: the first is the cover, the rest go inside the body
newBlogTitleNocreate a new blog with this title and put the article in it
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.5/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, images are copied into the store as the featured image, scheduling happens natively on Shopify, an over-long tag is refused rather than truncated, and pre-existing installs need to re-approve a permission. It also warns that view counts do not exist and must never be quoted, which prevents a concrete failure mode.

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 condition, then behavior, then routing; nearly every clause carries actionable information. It runs long and packs several unrelated facts (credits, permissions, view counts) into one block, but nothing is pure 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 23-parameter mutation with no output schema, the description covers the return ('Shopify's own copy of the article, with its public address once published'), the permission edge case, and the image/video placement rules. Minor gaps remain around idempotency/duplicate handling and why the tool is flagged destructive, both of which exist only in the schema.

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?

With 100% schema coverage the baseline is 3, and the description adds real cross-parameter semantics: status 'scheduled' requires a future `date`, the first image becomes the featured image while the rest go inline, `blog` is unnecessary on a single-blog store, and `newBlogTitle` creates a blog. Fields like hook, ideaId, recipe and the SEO fields 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 set (publish, draft, schedule) plus a precise resource (a blog article on the Shopify store's blog), and the title/description reinforce the same scope. An agent can immediately distinguish this from product publishing or the other channel-posting siblings.

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?

The opening sentence gives the trigger condition explicitly, and it routes to a concrete helper for blog selection (list_shopify_blogs) when the store has several blogs. It also covers the setup prerequisite (installed from the Shopify App Store, no tile to connect), though it never states when not to use it, e.g. versus publish_to_shopify_product.

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