Skip to main content
Glama
Upload-Post

Upload-Post

Official

Edit Google Business location info

update_google_business_location
DestructiveIdempotent

Edit the public Google Business location info shown on Google Search and Maps, from description and hours to categories; validate changes first or run a dry run before they go live.

Instructions

Edit the public info of the Google Business location (what shows on Google Search and Maps). edit_mode legacy (default): only description, website, phone, additional_phones, regular_hours, special_hours, primary_category, additional_categories; an empty value clears the field. edit_mode strict: also title, address, service_area, more_hours, open_status (OPEN, CLOSED_TEMPORARILY, CLOSED_PERMANENTLY), opening_date, store_code, labels; an empty value leaves the field as it is and null clears it; title, address, primary_category, phone and closing the business need confirm, and dry_run checks the change with Google without applying it. validate_only checks with Google in both modes. Read the current values first with google_business_read location_info. Changes go live on 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": {
      "user": "<user>",
      "fields": "<fields>"
    },
    "name": "update_google_business_location"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYesUpload-Post profile name with Google Business connected.
fieldsYesThe fields to change, with the API's names (e.g. { description: '…', regular_hours: [...] }).
confirmNoThe API's own confirmation for deletions and other changes that cannot be undone. Set it to true only after the user has approved that exact change; without it those actions are refused and nothing changes.
dry_runNostrict only: validate and show what would be sent; nothing is changed.
edit_modeNoDefault legacy.
location_idNoLocation: locations/123, 123 or accounts/456/locations/123 (see get_google_business_locations). Needed when the profile has several.
validate_onlyNoValidate with Google; nothing is changed.
include_edit_statusNostrict only: include each field's edit status (default true).

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.25.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already flag destructive=true, openWorld=true and idempotent=true, but the description adds critical semantics: 'Changes go live on Google', empty values clear fields in legacy mode yet are ignored in strict mode where `null` clears instead, and certain edits are refused without `confirm`. The only shortfall is that it does not clarify irreversibility of a live edit beyond the confirm gate.

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?

Single dense paragraph where each clause carries operative information about modes, confirmations, and clearing behavior. The long field enumerations are necessary content rather than padding, though the mode split could be structured more scannably.

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?

An output schema exists, so return values need not be explained. Given eight parameters, nested `fields` object, and a destructive live-write tool, the description covers modes, confirmation requirements, validation options, and a prerequisite read step.

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 coverage is 100%, so baseline is 3, but the description goes further by defining per-mode field availability and the empty-value versus `null` clearing distinction, which the schema does not convey. It also ties `dry_run` to strict mode only and `validate_only` to both, adding meaning beyond the parameter list.

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: editing the public info of a Google Business location, scoped to what appears on Search and Maps. It is clearly distinct from the sibling read tool, which it explicitly names for reading current values.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to read current values first via google_business_read location_info, then lays out the two edit modes and which fields each accepts. It also states when `confirm` is required and what `dry_run`/`validate_only` are for, so the agent knows both the precondition and the safe-check path.

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