Skip to main content
Glama
Upload-Post

Upload-Post

Official

Manage Google Business

manage_google_business
Destructive

Edit Google Business location details beyond basic info—attributes, menus, services, lodging, media, booking links, review replies, reports, and account groups—with preview-and-confirm changes.

Instructions

Change the Google Business location connected to user beyond its basic info (edit that with update_google_business_location). Fields go in params with the API's names; changes go live on Google Search and Maps, and Google allows about 10 edits per minute per location (429 location_edit_rate_limited). dry_run validates without applying where supported. update_attributes (attributes, whatsapp_url, text_messaging_url, remove: only the attributes named change; see google_business_read available_attributes); answer_google_updates (decision accept|reject, fields: keep or undo Google's own changes; title and storefront fields need confirm); update_lodging (lodging, update_mask; null clears a field, lists are replaced whole; needs confirm); replace_food_menus (menus: the WHOLE list, anything left out is removed, null removes all; needs confirm) and replace_services (service_items, the whole list; needs confirm): read them first with google_business_read; gallery: upload_media (source_url public link, category COVER|PROFILE|EXTERIOR|INTERIOR|PRODUCT|AT_WORK|FOOD_AND_DRINK|MENU|COMMON_AREA|ROOMS|TEAMS|ADDITIONAL, description; photos at least 250 px and 10 KB), update_media_category (media_name or media_key, category: the only editable field), delete_media (media_name or media_key; cannot be restored; needs confirm); booking and ordering links: create_place_action (type, uri, is_preferred), update_place_action (link, uri, is_preferred, is_disabled), delete_place_action (link, needs confirm); delete_review_reply (review_name, or review_id + location_id: removes the owner's public reply); report_google_location (google_location from search_google_locations, reason_bad_location or reason_bad_recommendation, elaboration; needs confirm, cannot be withdrawn); create_account_group (type LOCATION_GROUP|USER_GROUP, account_name, primary_owner; needs confirm). Needs the user's approval: call it first without confirmed to get a preview (nothing is sent), show the user exactly what will go out, and repeat the call with confirmed: true only after they approve.

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>",
      "user": "<user>"
    },
    "name": "manage_google_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
userYesUpload-Post profile name with Google Business connected.
actionYes
paramsNoOther API fields for this action, with the REST API's own names (snake_case) and shapes. See the description for each action's fields. Leave out what you do not want to change.
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.
confirmedNoSet to true only after the user has seen the preview this tool returns without it and approved it. Without it nothing is sent.
location_idNoLocation: locations/123, 123 or accounts/456/locations/123 (see get_google_business_locations). Needed when the profile has several.

Output Schema

NameRequiredDescriptionDefault
resultNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.26.5

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructiveHint and openWorldHint, but the description adds far more: edits go live publicly on Search and Maps, a ~10 edits/minute rate limit with the 429 location_edit_rate_limited error, and a dry_run validation path. It also discloses irreversibility per action ("cannot be restored", "cannot be withdrawn") and spells out the two-step confirmed preview/approval flow, which the annotations alone could not convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The scoping constraint and rate limit are front-loaded correctly and nearly every clause carries real information, so there is little padding. However, the bulk is delivered as one enormous semicolon-and-parenthesis run-on, making the 14 per-action sub-specs hard to scan or look up while choosing an action.

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-action mutation tool with nested params and an output schema, the description covers every action's fields, its confirmation requirements, and which reads must precede destructive replacements. Nothing an agent needs to pick an action and avoid an irreversible mistake is missing, and return values are left to the output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 83%, so baseline would be 3, but the description supplies per-action field semantics the schema's generic `params` bag cannot: `null` clears a field, lists are replaced whole, media category is the only editable field, source_url must be a public link, photos need 250 px / 10 KB minimum, and the full COVER|PROFILE|... enum. It also clarifies the `confirm` vs `confirmed` distinction beyond the schema's own wording.

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 ("Change the Google Business location connected to `user`") and immediately scopes out the sibling case with "beyond its basic info (edit that with update_google_business_location)." An agent can distinguish this from update_attributes-style siblings without opening the schema.

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 routes the agent: use update_google_business_location for basic info, read first with google_business_read / available_attributes, and use search_google_locations before report_google_location. It also names the alternative read path for menus, services and attributes before replacement, which is exactly the when-to-use guidance that prevents data loss.

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