Skip to main content
Glama
hermoso-ai

Hermoso

Official

Post to Google Business Profile

post_to_google_business

Publish posts to Google Business Profile with text, photo, and call-to-action button, appearing immediately on Google Search and Maps. Confirm details with the user before publishing.

Instructions

Publish a Post to the brand’s Google Business Profile — the panel that appears on Google Search and Maps for the business. Text, optionally ONE PHOTO, and a call-to-action button. Google’s Posts API accepts NO VIDEO, so pass a still image. This PUBLISHES immediately and publicly on the business listing — show the user the exact text, photo and button and get an explicit yes BEFORE calling. If the account manages several listings, call list_business_locations first and pass locationId. EVENT and OFFER posts both REQUIRE a title and a start date (Google’s rule). On an OFFER, Google IGNORES the button’s link — pass redeemOnlineUrl instead. A CALL button dials the number on the listing and takes no link. Needs Google Business Profile connected (Settings ▸ Connectors ▸ Google Business Profile).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hookNoWHAT ANGLE THIS POST IS BUILT ON — the single most valuable field here, and the only moment it can ever be recorded. post_performance groups on it to answer "which hooks work", and it needs 5 posts sharing ONE hook before it will call anything a winner, so REUSE THE SAME WORDING across a campaign instead of rephrasing it every time. Best of all, pass a hook id from list_hooks (e.g. "direct_callout", "mid_problem", "before_after") — those fold onto a stable key however they are spelled, so a whole brand accumulates evidence on one row. Your own wording is fine too; it just only groups when you repeat it exactly. Omitting it means this post can never vote on which hook works.
linkNothe URL the button opens — not for CALL, and ignored on an OFFER
titleNoheadline — REQUIRED for EVENT and OFFER
endDateNoYYYY-MM-DD, defaults to startDate
subjectNoWHAT THIS POST IS ABOUT — the product, feature, offer or theme (e.g. "winter coat", "free trial", "founder story"). The second grouping axis in post_performance. Same rule as hook: reuse the exact wording so posts about one subject land in one group.
summaryNothe body text of the Post
imageUrlNoa Hermoso render image URL (or an upload_file url) to show on the Post
startDateNoYYYY-MM-DD — REQUIRED for EVENT and OFFER
topicTypeNodefault STANDARD
actionTypeNothe button on the Post
couponCodeNoOFFER only
locationIdNowhich listing, e.g. 'locations/123' from list_business_locations — only needed when the account manages more than one
languageCodeNoBCP-47 language of the Post, default 'en'
redeemOnlineUrlNoOFFER only — this is the link Google actually uses on an offer
termsConditionsNoOFFER only

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.161

TDQS

A4.6/5.0
Behavior5/5

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

The description goes well beyond the annotations by warning that the tool PUBLISHES immediately and publicly and by requiring explicit user confirmation. It also discloses platform-specific behaviors Google imposes: no video, EVENT and OFFER requiring a title and start date, OFFER ignoring the button link, and CALL taking no link.

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?

The description is front-loaded with the core purpose and then packs only high-value safety and platform constraints into concise sentences. The capitalized warnings draw attention to the behaviors that matter most without adding 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 15-parameter, immediately public publish operation with no output schema, the description covers the critical prerequisites, side effects, consent step, and Google-specific rules. The only minor omission is the absence of any statement about the expected response or error behavior, but that is secondary for this kind of tool.

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?

The schema already documents all 15 parameters at 100% coverage, so the description is not required to re-describe each field. It adds useful cross-parameter meaning by tying EVENT/OFFER to title and startDate, explaining the ONE PHOTO rule, and clarifying that locationId comes from list_business_locations.

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?

The description states the exact action and target: publish a Post to the brand's Google Business Profile, and it explains what the post contains and where it appears (Google Search and Maps). This clear verb-plus-resource framing separates it from the other post_to_* sibling tools.

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?

It gives explicit preconditions: show the user the full post and get consent before publishing, call list_business_locations first when several listings exist, and have the Google Business Profile connector connected. It does not explicitly enumerate alternatives or when not to use this tool, but the Google-specific context makes the intended use 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