Hermoso is a marketing MCP server: 906+ tools over one OAuth’d endpoint that let an agent research the ads already running in a market, generate finished image and video ads, publish them, and build the paid campaigns behind them. Grok Bot reaches all of it through one connection. This page covers one slice of that: what Grok Bot can actually do on Pinterest, and what Pinterest will not let it do.
Connect Hermoso to Grok Bot
- Fastest: add the Hermoso Marketing Bot template. Open the template and add it to Grok Bot. It arrives wired to Hermoso but with no key, because templates never carry secrets, so it asks for one: create a key under MCP & CLI → Terminal & API keys and paste it into the Bot’s chat. A key carries real spend authority, so treat it like a password.
- Or sign in from the Bot’s own terminal. Every Bot gets a browser, a filesystem and a shell, so the keyless install works there too:
Thenpm install -g hermoso && hermoso auth loginhermosocommand is then available to the Bot with nothing pasted into a config file. Settings → Plugins is a catalog of pre-built connectors that does not list Hermoso, so the template and the terminal are the ways in today. - Using Grok Build instead? xAI’s terminal coding agent is a separate product with its own setup: see Hermoso in Grok Build.
- Ask a Bot for something. “Pull my three closest competitors’ longest-running ads and remix the best hook into a 9:16 video,” or “post this render to the channel.” The agent picks the tools; you approve the spend.
Hermoso is not affiliated with or endorsed by xAI and does not claim to be. The Hermoso Marketing Bot template is published by Hermoso; the same steps are in the app under MCP & CLI, on the Grok Bot tab of the agent setup.
Then connect Pinterest itself, once, under Settings → Connectors in Hermoso. That is an OAuth consent screen, so it is the one step that needs a browser. Everything after it is a tool call.
The Pinterest tools Grok Bot gets
list_pinterest_boards: the account’s boards, including secret ones, with their ids.create_pinterest_board: makes a new board.post_to_pinterest: creates an image or video Pin on a board you name, with a title, a description, a destination link and alt text.schedule_post: queues the Pin, carryingboardId.list_pinterest_ads_campaigns / pinterest_ads_report: read the paid side.
The limit you need before you plan a Pinterest workflow: this app holds Trial access, and Pinterest refuses Pin creation in production on Trial. Their words, caught on the first real Pin: “Apps with Trial access may not create Pins in production.” Boards and reads do work on Trial (listing boards, creating boards, reading Pins), and Hermoso’s error names the access tier rather than telling you to reconnect, because reconnecting cannot fix it. An upgrade to Standard access is what unblocks Pin creation, and it is pending review. The same tier limits the paid side: on Trial, Pinterest exposes no ad accounts at all.
Pinterest limits worth knowing before you automate anything
| Text | A Pin description is capped at 800 characters and a Pin title at 100. It is enforced when the post is created or queued, so an overlong post is refused while you are still there to fix it instead of being silently cut on the way out. |
|---|---|
| Visibility | Public, and the control is the board rather than the Pin. A Pin inherits its board’s public or secret state, so “post it somewhere private” is expressed by choosing a secret board. That is why the board is a required argument rather than a default. |
| Carousel | 2 to 5 images, images only. Both bounds come straight from Pinterest’s own v5 OpenAPI (minItems: 2, maxItems: 5), which is the only machine-readable source Pinterest publishes (their developer site is a client-rendered app that returns nothing to a fetch). There is no multi-video source, so a video slide is refused rather than dropped. |
| Which account | boardId, and it is the only identity field refused at enqueue rather than at publish time. Leave it out and nothing is scheduled, because “a Pin on the wrong board is a public mistake, so we never choose one for you.” |
Try it in Grok Bot
Ask for it in ordinary language. These are plain sentences, not a DSL:
“For every new product this week, generate a vertical Pin image with a title and description and stage it against the right board.”
That walks list_pinterest_boards → plan_ad → generate_image → post_to_pinterest. Approval is Grok Bot’s setting rather than ours, and the shared machine is the reason to think about it: isolation is per user, not per Bot, so anything one Bot connects, every Bot on that machine can reach.
Grok Bot on Pinterest: the part that bites
Do not point a persistent agent at Pin creation and let it keep trying. Pinterest refuses it in production for apps on Trial access, which is an access tier rather than a transient failure, and Hermoso's error names the tier so a Bot can tell the two apart instead of burning a night on retries. Boards read and write, so staging the whole set is real work that survives until Standard access lands.
For a long unattended run the hermoso CLI is the cheaper path: the agent shells out per command instead of carrying an 906+ tool manifest through every turn of a job that might run for days.
Research Pinterest before you post
There is no Pinterest ad library, so competitor research on Pinterest is not something Hermoso claims. The creative you would run there is well covered by the rest of the studio: make_template_ad and the image models produce the vertical, text-forward stills the surface rewards.
The paid half
Pinterest Ads tools exist for a campaign, an ad group and an ad that promotes an existing Pin, with archiving instead of deleting, because Pinterest’s ADS API has no delete verb (organic Pins and boards do delete, through delete_pinterest_pin and delete_pinterest_board; it is the paid objects that can only be archived). But the same Trial-access tier that blocks Pin creation exposes no ad accounts, so ad writes are not usable until Standard access lands. That is the honest state, and it is better in a sentence here than discovered on a deadline.
What Grok Bot cannot do on its own
An agent with a budget is only useful if the blast radius is bounded, so the fence is in the server rather than in a prompt. Every ad campaign, ad set, ad group and ad is created paused, and the status switches that arm real money refuse to run without an explicit confirmation flag. Every render is quoted first (hermoso_capabilities publishes each model’s exact credit cost before anything spends). Credits are reserved before the first provider call and settled at the exact cost afterwards, so a failed dispatch refunds rather than leaving you billed for nothing. Deletes are confirm-gated too, and every campaign tree is read back from the ad platform before your agent tells you what it built.
One step is deliberately not headless: linking an account is an OAuth consent screen, so you connect the channel once in a browser. Everything after that is a tool call.
The rest of the matrix
From Grok Bot, post to: Facebook · Instagram · Threads · TikTok · YouTube · X · LinkedIn · Bluesky · Telegram. Or see everything Grok Bot can publish to.
Post to Pinterest from: Claude · ChatGPT · Claude Code · Cursor · Codex · Cline · OpenClaw · Hermes · Gemini CLI · Perplexity · Le Chat · Claude Cowork · Perplexity Computer · Paperclip
Frequently asked questions
Can Grok Bot post to Pinterest?
Yes, through Hermoso's MCP server. Add the Hermoso Marketing Bot template from x.ai/bot/THQqogUKuhn1whWU0hrmb, which arrives wired to Hermoso and asks for an API key you create under MCP & CLI, Terminal & API keys. Or run npm install -g hermoso && hermoso auth login in the Bot's own terminal, which stores the credential with nothing pasted. Grok Bot then has 906+ tools, including the ones that publish to Pinterest, plus the ones that research the ads already running in your market and render the creative in the first place.
How do I connect Pinterest to Grok Bot?
Two steps, once each. Add the Hermoso Marketing Bot template from x.ai/bot/THQqogUKuhn1whWU0hrmb, which arrives wired to Hermoso and asks for an API key you create under MCP & CLI, Terminal & API keys. Or run npm install -g hermoso && hermoso auth login in the Bot's own terminal, which stores the credential with nothing pasted. Then connect Pinterest inside Hermoso under Settings → Connectors, which is an OAuth consent screen in a browser. After that Grok Bot publishes to Pinterest as an ordinary tool call.
Can Grok Bot post privately or as a draft to Pinterest?
Visibility on Pinterest lives on the board, not the Pin: a Pin inherits its board’s public or secret state, which is why the board is a required argument rather than a default. Hermoso refuses a visibility Pinterest cannot honour at the moment you ask for it, rather than quietly publishing something weaker.
Can Grok Bot run Pinterest ads as well as posting?
The Pinterest Ads tools exist (campaign, ad group, and an ad promoting a Pin), but the same Trial-access tier that blocks Pin creation exposes no ad accounts, so ad writes are not usable until Standard access lands.
What is the Pinterest caption limit when posting from Grok Bot?
A Pin description is capped at 800 characters and a Pin title at 100. Hermoso enforces it when the post is created or queued, so Grok Bot is told immediately rather than failing later when nobody is watching.
Can Grok Bot research Pinterest before it posts?
There is no Pinterest ad library, and Hermoso does not claim competitor research there. The rest of the research surface is unaffected: the Meta, Google and LinkedIn ad libraries plus organic TikTok, Instagram, YouTube, Reddit and Threads.
Related
The long version, with the setup and what it did in practice: run your marketing with a Grok bot and autonomous marketing with a Grok bot.
The same bot on other channels: X, Instagram, TikTok, YouTube, Facebook, LinkedIn and Threads.
Start free with 30 credits at signup and 250+ more to earn. Every feature is on every plan. Credits are spent only on AI models and Ad Spy research; posting, scheduling, ads management and analytics are free.
Start free → See pricing