Skip to main content
Glama
jie8357IOII

google-my-business-mcp

by jie8357IOII

gmb_accounts_accounts_list

Read-onlyIdempotent

List all Google Business accounts accessible to the authenticated user, including owned and managed accounts. Supports filtering by account type and pagination to retrieve results.

Instructions

GET v1/accounts. Lists all of the accounts for the authenticated user. This includes all accounts that the user owns, as well as any accounts for which the user has management rights.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoSelector specifying which fields to include in a partial response.
filterNoOptional. A filter constraining the accounts to return. The response includes only entries that match the filter. If `filter` is empty, then no constraints are applied and all accounts (paginated) are retrieved for the requested account. For example, a request with the filter `type=USER_GROUP` will only return user groups. The `type` field is the only supported filter.
$.xgafvNoV1 error format.
pageSizeNoOptional. How many accounts to fetch per page. The default and maximum is 20.
pageTokenNoOptional. If specified, the next page of accounts is retrieved. The `pageToken` is returned when a call to `accounts.list` returns more results than can fit into 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.
parentAccountNoOptional. The resource name of the account for which the list of directly accessible accounts is to be retrieved. This only makes sense for Organizations and User Groups. If empty, will return `ListAccounts` for the authenticated user. `accounts/{account_id}`.
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, so the safety profile is clear. The description adds useful behavioral context by clarifying that 'all accounts' includes owned and management-rights accounts, going beyond the annotation details.

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 description is two succinct sentences, front-loaded with the HTTP verb and resource name. Every word contributes meaning; there is no fluff or redundancy.

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?

Given the full schema coverage, clear annotations, and the simple nature of a list operation, the description is complete enough for an agent to select and invoke the tool correctly. It does not need to detail return values since no output schema exists and the purpose is straightforward.

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 the schema already thoroughly documents all parameters (fields, filter, pageSize, pageToken, parentAccount, etc.). The description adds no additional parameter-level semantics, so the baseline of 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 tool lists all accounts for the authenticated user, specifying that it includes both owned accounts and those with management rights. This uses a specific verb ('Lists') and resource ('accounts'), and distinguishes it from sibling tools like get (single account) or admins_list.

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?

The description provides clear context: it lists all accounts for the authenticated user, implying when this should be used. However, it does not explicitly mention alternatives or when not to use it, such as pointing to accounts_get for a specific account.

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