← Windsor.ai GBPCONTENT HISTORY

Update to Windsor.ai GBP

Snapshot Sep 30, 2026 · 22:59 UTC · version 1.0.0

Collection source: not recorded for this historical snapshot.

WHAT CHANGED · RULE-BASED ANALYSIS

First saved snapshot

No earlier snapshot is available to establish a change.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "name": "google-business-profile",
  "description": "Analyze Google Business Profile (Google My Business) listing performance and manage the profile through Windsor.ai. Use when the user asks about a location's views, searches, calls, direction requests, or reviews — or wants to publish or update a local post, reply to a review, upload a photo, update business info or hours, or set the open status. Do not use for Google Ads, other review platforms (Yelp, …), or generating post creative.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 540
    }
  ],
  "skill_md_contents": "---\nname: google-business-profile\ndescription: Analyze Google Business Profile (Google My Business) listing performance and manage the profile through Windsor.ai. Use when the user asks about a location's views, searches, calls, direction requests, or reviews — or wants to publish or update a local post, reply to a review, upload a photo, update business info or hours, or set the open status. Do not use for Google Ads, other review platforms (Yelp, …), or generating post creative.\n---\n\n# Google Business Profile via Windsor.ai\n\nWindsor.ai exposes live Google Business Profile (GBP / Google My Business) data\n(read) and profile management (write) through MCP tools. The connector id is\n`google_my_business`. On the Business Profile app the connector is already\nscoped; when a tool asks for a connector, use `google_my_business`.\n\nGolden rules:\n\n- **Never guess field, location, action, or option names** — get them from\n  `get_fields`, `get_connectors`, `list_actions`, and `get_options`. Call those\n  first.\n- **Reads are safe; writes are public and change the live listing.** Only call\n  `execute_action` after the user confirms the specific change.\n- Report what the user asked for, concisely.\n\n## 1. Ground yourself first\n\nCall `get_connectors` to see connected Business Profile locations. If none is\nconnected, help the user connect: `get_connector_authorization_url` (or\n`get_connector_connect_info`) and give them the setup link (GBP needs the\n`business.manage` scope). If several locations are connected, ask which one.\n\n## 2. Reading insights and reviews\n\n1. `get_fields` for `google_my_business` — insight metrics (impressions on maps\n   and search across desktop/mobile, `CALL_CLICKS`, `WEBSITE_CLICKS`, direction\n   requests, bookings, conversations) and review / local-post / media data. Use\n   the exact ids returned.\n2. `get_data` with the fields, target location `account`(s), and a date range.\n\n## 3. Managing the profile (write actions)\n\nCall `list_actions` first for exact ids/schemas. GBP exposes:\n\n- **`create_local_post` / `update_local_post`** — publish or edit a \"What's New\"\n  post (text, optional public photo URL, optional call-to-action button).\n- **`reply_to_review`** — publish (or replace) the owner's public reply to a\n  review.\n- **`upload_media`** — add a photo to the gallery (category ADDITIONAL / COVER /\n  PROFILE / …).\n- **`update_location`** — update the business description, website, and/or phone\n  (Google may review edits before they appear).\n- **`set_regular_hours` / `set_special_hours`** — replace the weekly hours or set\n  exceptional (holiday) hours; both replace all existing entries, so include\n  every period in one call.\n- **`set_open_status`** — mark the location OPEN or CLOSED_TEMPORARILY.\n\nWrite workflow — every time: resolve the target (post/review/location) to its id\nvia a `get_data` read if needed, build params from the `list_actions` schema,\n**show the user the exact change and confirm** (these are public and edit the\nlive listing), then call `execute_action` and report the result.\n\n## 4. Reference real data, don't fabricate\n\nOn an error, call the relevant discovery tool and retry with correct ids, or\nreport the specific error. Never invent metrics, review text, post ids, or hours.\n"
}

SHA-256: 3d00b905a42f7bdb5c91dcc4b345557260172c15098b850675e4974f4c6cf819