MCP server for Google Business Profile — manage posts, reviews, locations
12 tools with consistent naming (verb_noun pattern: list_, get_, create_, update_, delete_, reply_). All have descriptions (avg 95 chars, within 10-1024 range). Input schemas present for all tools with proper JSON Schema types. However, parameter descriptions are sparse or missing context; output schemas are undocumented; error handling lacks recovery guidance; no tool annotations (readOnlyHint/destructiveHint); no pagination metadata (total count, next_cursor) in list tools despite accepting pageSize/pageToken. Risk classifications visible in metadata but not in tool descriptions themselves.
Create a new post on a GBP location. Supports standard posts, event posts, and offer posts. Can include text, media (photo/video URL), and a call-to-action button.
Delete a GBP post
Delete a business reply to a review
Get a specific GBP post by its resource name
Get a specific review by resource name
List all Google Business Profile accounts accessible to the authenticated user
Output schemas undocumented. No visible schema definitions for tool return values. LLMs cannot infer what fields to expect (e.g., does listAccounts return account_id, name, email, or all three?). Breaks tool chaining and forces agents to guess field names.
List tools (gbp_list_accounts, gbp_list_locations, gbp_list_posts, gbp_list_reviews) accept pageSize and pageToken but do not document pagination metadata in return (total count, next_cursor, has_more). Without this, agents cannot determine if more results exist or how to fetch them efficiently.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 57 | 2026-07-28+ | v2 |
List all locations (businesses) for a GBP account. Use gbp_list_accounts first to get the account ID.
List media items (photos/videos) for a GBP location
List local posts for a GBP location
List reviews for a GBP location
Reply to a review on behalf of the business
Update an existing GBP post's text and/or call-to-action
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) in tool definitions. Risk classifications exist in metadata (READ_ONLY, WRITE, DESTRUCTIVE) but are not exposed via MCP tool annotations. Agents cannot determine which tools are safe to retry or have side effects.
Error handling lacks recovery guidance. No visible error messages that tell LLMs what to do next (e.g., 'User not found. Try search_users() first.'). Raw API errors (e.g., 'GBP API error 404') provide no actionable next step.
gbp_create_post has 14 optional parameters with interdependencies (e.g., eventTitle required if topicType='EVENT', offerCouponCode required if topicType='OFFER'). These constraints are not documented in parameter descriptions. LLMs will pass invalid combinations without guidance.