Skip to main content
Glama

list_google_business_locations

Read-onlyIdempotent

Read a Google Business location profile or look up Google Business categories. view=profile (default): read title, description, primary and additional categories, services, phone numbers, website URL, regular opening hours, attributes, and pending-review status for one location (pass account_id or location_id). view=categories: search Google Business categories via categories.list (region_code and language_code required, optional prefix filter, category_view BASIC or FULL, page_size up to 100, page_token). Stays off until location edits are switched on, and does not call Google while it is off.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
viewNoprofile (default) or categories.
prefixNocategories: optional category display name prefix filter.
page_sizeNocategories: max results per page (1 to 100, default 50).
account_idNoGoogle Business account ID from list_accounts.
page_tokenNocategories: next_page_token from a previous categories response.
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.
region_codeNocategories: two-letter ISO country code, e.g. US or GB.
workspace_idNoFilter to a workspace ID from whoami.
category_viewNocategories: BASIC (default) or FULL (includes service types and more-hours types).
language_codeNocategories: BCP-47 language code, e.g. en or en-GB.
include_google_updatedNoprofile: when true, also check Google-suggested updates (the getGoogleUpdated method).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / category_view
      Added value: +{
      +  "description": "categories: BASIC (default) or FULL (includes service types and more-hours types).",
      +  "enum": [
      +    "BASIC",
      +    "FULL"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / include_google_updated
      Added value: +{
      +  "description": "profile: when true, also check Google-suggested updates (the getGoogleUpdated method).",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / language_code
      Added value: +{
      +  "description": "categories: BCP-47 language code, e.g. en or en-GB.",
      +  "type": "string"
      +}
    • addedInput schema / properties / page_size
      Added value: +{
      +  "description": "categories: max results per page (1 to 100, default 50).",
      +  "maximum": 100,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / page_token
      Added value: +{
      +  "description": "categories: next_page_token from a previous categories response.",
      +  "type": "string"
      +}
    • addedInput schema / properties / prefix
      Added value: +{
      +  "description": "categories: optional category display name prefix filter.",
      +  "type": "string"
      +}
    • addedInput schema / properties / region_code
      Added value: +{
      +  "description": "categories: two-letter ISO country code, e.g. US or GB.",
      +  "type": "string"
      +}
    • addedInput schema / properties / view
      Added value: +{
      +  "description": "profile (default) or categories.",
      +  "enum": [
      +    "profile",
      +    "categories"
      +  ],
      +  "type": "string"
      +}
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint, non-destructive), so the description adds real value by disclosing the gating behavior: the tool stays off until location edits are switched on and makes no Google call while off. It also names the backing method (categories.list / getGoogleUpdated) via include_google_updated, which hints at the underlying call shape.

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?

Three sentences, front-loaded with the two modes and then the per-mode requirements; nothing is filler. The middle sentence is a long comma-separated field list, which is dense but justified since no output schema exists.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 11 optional parameters, two views, and no output schema, the description does the necessary work: it explains both modes, the per-mode required inputs, and the profile field set that a caller would otherwise have to discover. The categories-mode response shape is only implied via page_token, which is a minor gap.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter is already documented in the schema, including the account_id-vs-location_id preference and the ChIJ Place ID warning. The description largely restates those constraints (region/language required, page_size up to 100, BASIC vs FULL) rather than adding new semantics, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ("Read a Google Business location profile or look up Google Business categories") and enumerates the returned fields, so the two modes are unambiguous. It does not explicitly contrast itself with manage_google_business_location or the sibling list_google_business_* tools, leaving the read-vs-manage boundary implicit.

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?

It gives clear per-mode routing: view=profile is the default and takes account_id or location_id, while view=categories needs region_code and language_code. What's missing is when to choose this over a sibling list tool or what to do when the feature is disabled beyond the fact that it is.

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