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, optional photo, and call-to-action button. Supports standard, event, offer, and alert types; confirms with user before immediate publication.

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
Behavior5/5

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

Annotations are minimal (readOnlyHint false, destructiveHint false, etc.), but the description adds critical behavioral context: it publishes immediately and publicly, requires explicit user confirmation before calling, and explains platform quirks like Google ignoring the button link on OFFER posts and CALL buttons dialing the listing's number. These details are beyond the annotations and are essential for safe, correct usage.

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?

The description is dense but well-organized: it leads with the core action, then constraints (no video, immediate publish, consent), then usage hints (locationId, connection), then platform-specific rules. Every sentence contributes new information; it is lengthy but warranted given the tool's complexity. It is not tautological or padded.

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 15-parameter publishing tool with no output schema, the description covers essentials: prerequisites (connection, locationId), behavioral caveats (immediate public publish, confirmation), special cases (event/offer requirements, offer link ignoring, call button), and points to schema for parameter details. Nothing an agent needs to call it correctly is omitted.

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 description coverage is 100%, and many parameters have rich descriptions (e.g., hook explains grouping semantics). The tool description supplements this by clarifying cross-parameter constraints: EVENT/OFFER require title and startDate, OFFER uses redeemOnlineUrl instead of link, and CALL ignores link. This adds meaningful meaning beyond the schema, though it does not enumerate every parameter—that is already handled by 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?

The description opens with a specific verb and resource: 'Publish a Post to the brand’s Google Business Profile'. It clearly distinguishes this from other post_to_* siblings by naming the platform (Google Search and Maps) and stating it accepts only text, one photo, and a CTA button. The 'NO VIDEO' note further narrows scope, making the tool's purpose unmistakable.

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 description gives concrete usage guidance: call list_business_locations first when managing multiple listings, requires a connected Google Business Profile (with Settings path), and specifies that EVENT/OFFER posts need a title and start date. It does not explicitly name alternative tools for other platforms, but given the tool name and the ecosystem, this is implicitly clear. The guidance is thorough enough to route an agent correctly.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hermoso-ai/hermoso'

If you have feedback or need assistance with the MCP directory API, please join our Discord server