Skip to main content
Glama

Google Business Profile & Local SEO Checker

Audit a local business end to end

audit_business
Read-onlyIdempotent

START HERE. One call: checks the Google profile name against the rules AND against the business's own website, benchmarks review count and rating against real Australian businesses in the same Google category, recommends the primary category from what real businesses in that trade use, audits the website's local SEO layer, and returns a priority-ordered action list. Call it with whatever the user has already said; it reports what each missing field would have added instead of demanding it up front.

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": {
      "business_name": "<business_name>"
    },
    "name": "audit_business"
  }
}

Input Schema

NameRequiredDescriptionDefault
tradeNoOptional: what they do in plain English, e.g. electrician, hair salon, carpet cleaning
ratingNoOptional: current Google star rating, e.g. 4.6
suburbNoOptional: main suburb or city
websiteNoOptional but worth asking for: their website. Settles the business-name question and adds the site audit
categoryNoOptional: the current Google primary category, if they know it
review_countNoOptional: current Google review count
business_nameYesName exactly as it appears on the Google profile
service_area_businessNoTrue if they travel to the customer (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real behavioral value beyond them: partial-data tolerance, that missing fields are reported as foregone value rather than blocking, and the shape of the deliverable as a priority-ordered action list. It does not describe how the website check behaves when no website is supplied, which keeps it from a 5.

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 imperative 'START HERE' is front-loaded and the whole definition is three sentences with no filler. The middle sentence is a long compound list of capabilities, which is dense but each clause corresponds to a distinct outcome the agent needs to know.

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 an 8-parameter, no-output-schema tool the description covers what comes back (action list, benchmarked figures, category recommendation) and how partial input is handled, which is the main ambiguity an agent would face. It could say more about the returned structure given there is no output schema, but the summary is adequate for correct invocation.

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 coverage is 100% with per-parameter descriptions, so the schema carries most of the load and a 3 baseline applies. The description does contribute one cross-parameter insight — that everything besides business_name is effectively optional and the call degrades gracefully — but it adds no syntax or format detail beyond the schema.

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 names a composite but concrete set of operations: profile-name rule check, website cross-check, review benchmark against Australian businesses in the same Google category, primary-category recommendation, local SEO audit, and a priority-ordered action list. 'START HERE' plus 'one call' makes clear it is the aggregating entry point, which differentiates it from the granular siblings like check_business_name or benchmark_business without needing to enumerate them.

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 opening 'START HERE' and 'Call it with whatever the user has already said' give explicit invocation guidance, including the important case of partial input and what happens to missing fields. It does not state any when-not conditions or name a sibling to prefer in a narrower scenario, so it stops short of a full routing rule.

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.

Resources