Skip to main content
Glama

manage_google_business_location

DestructiveIdempotent

Update a Google Business location profile, hours, or attributes (one field group per call). Actions: update_hours (regular_hours.periods), update_attributes (attributes), update_description (description, max 750 chars, no URLs or phone numbers), update_categories (categories with primary_category and up to 9 additional_categories; carries over existing additional categories when omitted), update_services (service_items, replaces the full list or clears services when empty; free-form categories must belong to the location), update_title (title), update_phones (phone_numbers with primary_phone and up to 2 additional_phones; carries over existing additional phones when omitted), update_website (website_uri). Every action uses preview then confirm with a one-time token: call without confirm to get a preview and preview_id, show it to the user, then call again with confirm=true and that preview_id. Title and primary category edits warn that Google may hold the change for review and that an inaccurate name or category can get the listing suspended. Stays off until location edits are switched on; a confirm while it is off changes nothing and does not call Google.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "manage_google_business_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoupdate_title: public business title on Google.
actionYesWhich location field group to update.
confirmNoLeave out to get a preview. Set true only after the user explicitly approved it, with the preview_id.
account_idNoGoogle Business account ID from list_accounts.
attributesNoupdate_attributes: [{ name, value_type, values }]. value_type is BOOL, URL, or ENUM. URL values must be https.
categoriesNoupdate_categories: { primary_category, additional_categories? } with categories/gcid:... resource names (max 9 additional; existing additional categories are carried over when omitted).
preview_idNoThe preview_id from the preview call. Required with confirm: true for actions that preview first.
descriptionNoupdate_description: business description (max 750 chars, no URLs or phone numbers).
location_idNoGoogle Business numeric location id (the location_id/platform_user_id from list_accounts, e.g. "197940849675145390"). NOT the ChIJ... Place ID from list_google_business_reviews view=review_link. Prefer account_id.
website_uriNoupdate_website: public website URL (http or https).
workspace_idNoFilter to a workspace ID from whoami.
phone_numbersNoupdate_phones: { primary_phone, additional_phones? } (up to 2 additional; existing additional phones are carried over when omitted).
regular_hoursNoupdate_hours: { periods: [{ open_day, close_day, open_time, close_time }] }. Days are MONDAY-SUNDAY. Times are HH:MM.
service_itemsNoupdate_services: full replacement list of structured_service_item or free_form_service_item entries (pass [] to clear all services).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • changedInput schema / properties / action / description
      Previous value: -"update_hours or update_attributes."New value: +"Which location field group to update."
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "update_hours",
      -  "update_attributes"
      -]New value: +[
      +  "update_hours",
      +  "update_attributes",
      +  "update_description",
      +  "update_categories",
      +  "update_services",
      +  "update_title",
      +  "update_phones",
      +  "update_website"
      +]
    • addedInput schema / properties / categories
      Added value: +{
      +  "description": "update_categories: { primary_category, additional_categories? } with categories/gcid:... resource names (max 9 additional; existing additional categories are carried over when omitted).",
      +  "properties": {
      +    "additional_categories": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "maxItems": 9,
      +      "type": "array"
      +    },
      +    "primary_category": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / description
      Added value: +{
      +  "description": "update_description: business description (max 750 chars, no URLs or phone numbers).",
      +  "maxLength": 750,
      +  "type": "string"
      +}
    • addedInput schema / properties / phone_numbers
      Added value: +{
      +  "description": "update_phones: { primary_phone, additional_phones? } (up to 2 additional; existing additional phones are carried over when omitted).",
      +  "properties": {
      +    "additional_phones": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "maxItems": 2,
      +      "type": "array"
      +    },
      +    "primary_phone": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / service_items
      Added value: +{
      +  "description": "update_services: full replacement list of structured_service_item or free_form_service_item entries (pass [] to clear all services).",
      +  "type": "array"
      +}
    • addedInput schema / properties / title
      Added value: +{
      +  "description": "update_title: public business title on Google.",
      +  "maxLength": 300,
      +  "type": "string"
      +}
    • addedInput schema / properties / website_uri
      Added value: +{
      +  "description": "update_website: public website URL (http or https).",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing the two-step preview/confirm protocol with a one-time preview_id, which fields are replaced versus carried over (additional_categories, additional_phones, full replacement of service_items), and that a confirm while location edits are disabled changes nothing and never reaches Google. It also warns that title and primary-category edits may be held for review or suspend the listing, which is exactly the risk context the destructiveHint annotation cannot convey.

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?

Front-loaded with the purpose and action map, then the workflow, then the warnings — a sensible order. The single dense paragraph runs long and repeats a couple of schema constraints (the 750-char limit appears twice), but for eight distinct actions the length is largely earned.

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 14-parameter destructive mutation tool with nested objects and no output schema, the description covers the workflow, the per-action payload semantics, the gating condition, and the failure modes that matter. What the preview response contains beyond preview_id is the only notable omission.

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 already 100%, so the baseline is 3, and the description adds real meaning on top: the max-9/2 sibling-collection limits, the carry-over- when-omitted semantics, the empty-list clearing behavior for services, and the 750-char/no-URL rule. Some of this duplicates the schema fields verbatim rather than extending them.

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?

States a specific verb and resource ('Update a Google Business location profile, hours, or attributes') and then enumerates all eight concrete actions with the field each touches, so an agent can map an intended edit to a call without opening the schema. Siblings such as manage_google_business_media and manage_google_business_review are implicitly excluded by the enumerated scope.

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 'one field group per call' constraint plus the explicit preview-then-confirm workflow gives clear operating context, including the requirement to show the preview to the user before confirming. It does not explicitly name siblings to use for media/reviews/service areas, so routing away from this tool is left implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources