update_location

Update an existing location's business details — including its categories (general, Google primary, and additional), Google Business Profile attributes, and its service/product list. Identify the location by its locationId (the locationId returned by create_location). Pass only the fields you want to change — anything you omit is left as-is, and passing a field replaces its current value (pass an empty string to clear a text field, or the full new list to replace a list — except `name`, which can be renamed but never cleared, because a location with no name is rejected by every directory and fails to publish silently). The country can't be changed after a location is created. If you change the address without also passing coordinates, latitude/longitude are re-derived automatically. By default your change updates the shared details that every publisher inherits; to change a value for specific publishers only (e.g. a different description on Google vs. Facebook), pass applyToPublishers. Use specialHours for one-off date closures/hours (e.g. "mark this Sunday, Aug 2 2026, as closed") — any calendar date works, not just named holidays; use regularHours/moreHours for the standing weekly schedule and extra hour types. Saving queues the change to sync out to the connected directories automatically — it goes out about 15 minutes after the location's last edit (further edits in that window are batched into one sync), and a publisher-specific change (applyToPublishers) resubmits to just those publishers. Tell the user their change is saved and will sync out shortly, not that it is already live; use publish_location to push it to Google immediately. Returns the updated location. You don't pass an agency — it comes from your credentials. IN A CLIENT-PORTAL SESSION only the fields the portal itself exposes are writable; categories, publisher overrides, custom attributes, keywords, tags and UTM are REJECTED and named back to you in `rejected`. Tell the client which fields could not be changed and that their agency owns those — do not report a partial save as a complete one.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "update_location",
    "arguments": {
      "locationId": "string"
    }
  }
}

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "content": [
      {
        "type": "text",
        "text": "..."
      }
    ]
  }
}