Skip to main content
Glama

Google Business Profile & Local SEO Checker

Score a Google Business Profile

audit_gbp_profile
Read-onlyIdempotent

Scores a Google Business Profile out of 100 from the details you give (categories, reviews and review recency, photos, services, products, posts, links, hours, service area) and returns a priority-ordered fix list. Weighted by what actually brings in calls. Unknown fields are listed for checking, never counted as passes. Read the values off the profile (or ask the user) and pass what you have.

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": "audit_gbp_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoMain city/suburb
nameNoBusiness name on the profile
has_logoNoLogo set
has_coverNoCover photo set
hours_setNoOpening hours set
chat_linksNoChat/SMS/WhatsApp links set
booking_urlNoBooking link, or empty string if none
descriptionNoDescription text
website_urlNoWebsite link on the profile
photos_countNoTotal photos
review_countNoTotal reviews
address_shownNoStreet address visible on the profile
service_areasNoService areas listed
average_ratingNoStar rating, e.g. 4.8
products_countNoNumber of products
services_countNoNumber of services listed
opening_date_setNoOpening date set
primary_categoryNoPrimary category
posts_last_30_daysNoPosts in the last 30 days
reply_rate_percentNo% of reviews with an owner reply
reviews_last_30_daysNoReviews in the last 30 days
additional_categoriesNoAdditional categories ([] if none)
days_since_newest_reviewNoDays since the newest review
is_service_area_businessNoTrue if the business goes to customers (tradie, mobile service)
services_with_descriptionsNoServices that have a description

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations only cover the safety profile (read-only, idempotent, non-destructive); the description goes well beyond them, disclosing the scoring scale, the weighted model, the return shape, and a non-obvious rule that 'unknown fields are listed for checking, never counted as passes.' That rule materially changes how an agent should interpret a low score with sparse input, which is exactly the behavioral context annotations cannot carry.

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 score-and-fix-list outcome, with no filler. The parenthetical field list is dense but earns its place as a gathering checklist; only slight tightening is possible.

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 25-parameter, zero-required tool with no output schema, the description covers both sides: what to feed in and what comes back (score out of 100 plus ordered fixes). It leaves minor gaps such as whether a partial-input score is directly comparable and the exact return format, but nothing that would cause a mis-call.

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?

Schema coverage is 100% with per-parameter descriptions, so the baseline would be 3. The description adds grouping and emphasis the flat 25-field schema does not: it enumerates the profile areas being assessed (categories, reviews and recency, photos, services, products, posts, links, hours, service area), helping the agent know which facts to gather before calling.

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?

States a specific verb and resource ('Scores a Google Business Profile out of 100') and names what the input covers and what comes back ('a priority-ordered fix list'). That is enough to differentiate it from single-field checks like check_gbp_description or check_gbp_post, though no sibling is named explicitly.

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?

Gives concrete invocation guidance: 'Read the values off the profile (or ask the user) and pass what you have,' which tells the agent partial input is acceptable and where to source it. It stops short of naming alternatives (e.g., when to use this versus optimisation_checklist or audit_website_local_seo) or stating exclusions.

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.