Skip to main content
Glama

Business Profile: change the listing

gbp_update_profile
DestructiveIdempotent

Change a Business Profile listing: categories, description, service areas, services, website, phone. Public: the listing is what searchers see, so preview first (confirm false: Google checks the change and nothing is saved), show the person every before/after, and confirm only on their yes. Category and area ids come from gbp_find_options. Changing the main category also needs confirm_primary_category, because it moves where the business shows in search. Google reviews each edit before publishing it (usually minutes, sometimes longer) and may reject it, so the result says which fields are pending; check later with gbp_profile.

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": {
      "gbp_location_id": "<gbp_location_id>"
    },
    "name": "gbp_update_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneNo
confirmNoLeave false to preview: nothing changes and the preview shows exactly what would happen. Set true only after the user has agreed to this exact change.
websiteNoFull URL
descriptionNoThe whole new description, up to 750 characters, no links
add_servicesNo
service_areasNoReplace ALL service areas with these
add_categoriesNoAdditional category_ids to add
gbp_location_idYesFrom gbp_list_locations
remove_servicesNoService names to remove, as gbp_profile lists them
primary_categoryNocategory_id from gbp_find_options. The old main category stays as an additional one unless removed.
add_service_areasNoService areas to add, keeping the others
remove_categoriesNoAdditional category_ids to remove
remove_service_areasNoplace_ids or names of service areas to remove
confirm_primary_categoryNoSet true only when the person has agreed to change the MAIN category

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=true and idempotentHint=true, so the safety and mutation profile is covered. The description still adds meaningful behavior beyond that: Google moderates each edit asynchronously (minutes to longer), may reject it, and the response marks affected fields as pending. That is real added context, though it never spells out which fields get overwritten or what the response looks like. A 3 fits because the description adds some value on top of complete annotations but does not cover the operation's full behavioral picture.

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

Conciseness5/5

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

The opening clause is front-loaded with the resource and fields, and each following sentence adds a distinct operational fact (preview semantics, id sourcing, main-category caveat, moderation latency, follow-up). There is no repeated wording and no filler.

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?

With 14 parameters, no output schema, and a destructive async write, this definition covers what an agent needs to invoke it safely: the preview/confirm gate, the required prerequisite lookups, the extra confirmation flag for the primary category, and how pending edits are surfaced and rechecked. Nothing essential to a correct call is left out.

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 86%, so most parameter meaning is already documented, which sets a baseline of 3. The description still adds real interpretation: confirm=false means Google checks the change and nothing is saved, and confirm_primary_category exists because changing the main category moves where the business appears in search. That goes beyond the schema's terse field notes.

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?

The first sentence names a specific verb and resource plus the exact editable fields (categories, description, service areas, services, website, phone), which immediately separates it from the read-only gbp_profile sibling. An agent knows what this tool changes 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?

It gives explicit when-to-use rules tied to a workflow: preview with confirm=false first, show the person every before/after, set confirm true only on their yes. It also routes to specific siblings for prerequisites (gbp_find_options for ids) and follow-up (gbp_profile for pending status).

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.