Skip to main content
Glama
Upload-Post

Upload-Post

Official

Read Google Business

google_business_read
Read-only

Read Google Business Profile data for a connected user: posts, reviews, performance metrics, search keywords, location details, media, and catalogs. Use actions to fetch exactly the data you need.

Instructions

Read-only Google Business Profile data for the location connected to user. Fields go in params with the API's names; lists page with page_size and page_token (answer: next_page_token). list_posts, get_post (post_id: accounts/…/localPosts/…); get_review (review_name, or review_id + location_id), batch_reviews (location_ids, order_by newest|lowest|highest) — list reviews with get_google_business_reviews; performance (metrics, comma-separated, e.g. BUSINESS_IMPRESSIONS_DESKTOP_MAPS, CALL_CLICKS, WEBSITE_CLICKS, BUSINESS_DIRECTION_REQUESTS; start_date / end_date YYYY-MM-DD, up to 18 months back): daily series; search_keywords (start_month / end_month YYYY-MM): the searches that showed the location; location_info (read_mask): name, address, hours, phones, categories, open status; google_updates: changes Google suggests; list_locations (account, filter, order_by, read_mask); list_accounts; gallery: list_media, get_media (media_name, or media_key + location_id), list_customer_media, get_customer_media; catalogs: categories (region_code, language_code, query), batch_categories (names, language_code), chains (name), get_chain (chain); available_attributes, attributes; place_action_types, place_actions (booking and ordering links); food_menus, services, lodging (hotels).

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

Input Schema

NameRequiredDescriptionDefault
userNoUpload-Post profile name with Google Business connected (not needed for categories, chains).
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.
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.25.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already cover read-only, non-destructive, open-world, so the safety profile needs no restating. The description adds real behavior: list actions page via page_size/page_token with next_page_token as the answer, performance returns a daily series capped at 18 months back, search_keywords uses month granularity, batch_reviews supports order_by newest|lowest|highest. It does not mention rate limits or what happens on an unsupported action/field combination, which for a 24-action dispatcher would be valuable.

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?

Nearly every clause carries information, but it is delivered as one dense semicolon-delimited block that is hard to scan for a specific action. Grouping actions (posts, reviews, performance, locations, gallery, catalogs, menus) onto separate lines would preserve the content while making lookup far faster. No filler, but structure is the weak point.

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?

For a 24-action dispatcher this is close to sufficient: the action list, per-action fields, pagination contract, date formats, and one sibling hand-off are all present, and a declared output schema means return shapes need not be described. The remaining gap is field-level documentation for the five menu/attribute/service/lodging actions and any statement of auth or scope requirements per action.

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?

The `params` object is free-form (additionalProperties), so the description is effectively its only documentation, and it does substantial work: field names per action, resource-name shapes (accounts/…/localPosts/…, media_name vs media_key + location_id), date formats (YYYY-MM-DD, YYYY-MM), and concrete metrics examples. Coverage is uneven — available_attributes, attributes, food_menus, services and lodging list no fields at all, leaving those actions undocumented.

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?

Opens with a specific verb+resource+scope: 'Read-only Google Business Profile data for the location connected to `user`', then enumerates the 24 supported actions so an agent can map intent to action. The leading sentence slightly undersells the breadth (it also covers accounts, chains, categories, catalogs, which are not tied to a single location), but the enumeration resolves any ambiguity.

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?

Routing guidance is present where overlap exists: 'list reviews with get_google_business_reviews', plus the schema-level pointer to get_google_business_locations for resolving location_id. The action enumeration itself tells an agent which action serves which need. It stops short of stating prerequisites (which actions require `user` or `location_id` beyond the categories/chains exception) or when the tool should not be used at all.

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