Skip to main content
Glama
jie8357IOII

google-my-business-mcp

by jie8357IOII

gmb_info_accounts_locations_list

Read-onlyIdempotent

Lists Google Business Profile locations for a specified account, with support for filtering, sorting, pagination, and field selection to retrieve only the data you need.

Instructions

GET v1/{+parent}/locations. Lists the locations for the specified account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoSelector specifying which fields to include in a partial response.
filterNoOptional. A filter constraining the locations to return. The response includes only entries that match the filter. If `filter` is empty, then constraints are applied and all locations (paginated) are retrieved for the requested account. For more information about valid fields and example usage, see [Work with Location Data Guide](https://developers.google.com/my-business/content/location-data#filter_results_when_you_list_locations).
parentYesRequired. The name of the account to fetch locations from. * **Specific Account ID**: If the account is of type `AccountType.PERSONAL`, the response returns only locations directly owned by that account. For all other types (e.g., `AccountType.LOCATION_GROUP`), it returns all accessible locations. * **Wildcard (`-`)**: Using `accounts/-` identifies the authenticated user. This scope defaults to `AccountType.PERSONAL` but includes both directly and indirectly owned locations (e.g., those accessible via member groups).
$.xgafvNoV1 error format.
orderByNoOptional. Sorting order for the request. Multiple fields should be comma-separated, following SQL syntax. The default sorting order is ascending. To specify descending order, a suffix " desc" should be added. Valid fields to order_by are title and store_code. For example: "title, store_code desc" or "title" or "store_code desc"
pageSizeNoOptional. How many locations to fetch per page. Default value is 10 if not set. Minimum is 1, and maximum page size is 100.
readMaskNoRequired. Read mask to specify what fields will be returned in the response.
pageTokenNoOptional. If specified, it fetches the next `page` of locations. The page token is returned by previous calls to `ListLocations` when there were more locations than could fit in the requested page size.
quotaUserNoAvailable to use for quota purposes for server-side applications. Can be any arbitrary string assigned to a user, but should not exceed 40 characters.
prettyPrintNoReturns response with indentations and line breaks.
Behavior2/5

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. However, the description adds no extra behavioral context such as pagination, filtering behavior, or wildcard account handling. The 'GET' method and 'Lists the locations' are nearly redundant with the tool name and schema, offering minimal additional transparency.

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?

The description is extremely concise, using only two short sentences with no wasted words. It front-loads the HTTP method and endpoint, then states the purpose. While slightly redundant with the tool name, it remains efficient and readable.

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

Completeness2/5

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

The tool has 10 parameters and no output schema, yet the description only states the basic list action. It does not mention pagination, filters, sorting, or the response structure, leaving the agent to rely entirely on the schema. For a moderately complex list API, this is insufficiently complete.

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% (all 10 parameters have descriptions). The description adds no parameter-specific meaning beyond 'specified account,' which already exists in the parent parameter description. The schema carries the full burden, so a baseline 3 is appropriate.

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 description clearly states the action (Lists) and the specific resource (locations for the specified account). It distinctly identifies the tool's purpose among many sibling list tools (e.g., localposts, media, reviews) by using the resource name 'locations'.

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

Usage Guidelines2/5

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

No usage guidance is provided. The description does not mention when to use this list operation versus other location-related tools (e.g., get, patch), nor does it describe preconditions or alternatives. It is a restatement of the function without contextual direction.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/jie8357IOII/google-my-business-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server