Skip to main content
Glama

Google Business Profile & Local SEO Checker

Audit a website's local SEO

audit_website_local_seo
Read-onlyIdempotent

Fetches one public web page and checks its local SEO layer: title and H1 naming the service and area, click-to-call link, LocalBusiness schema, name and phone matching the Google profile, indexability, robots.txt, sitemap, mobile viewport, forms, review proof. Returns a score and a priority-ordered fix list. Only reads the page.

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": {
      "url": "<url>"
    },
    "name": "audit_website_local_seo"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPage to check, usually the homepage or the page the Google profile links to
phoneNoOptional: phone as on the Google profile
suburbNoOptional: main suburb/city
main_serviceNoOptional: main service, e.g. 'electrician'
business_nameNoOptional: name as on the Google profile

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive behavior, so the bar is low. The description still adds value by listing what gets inspected and by stating the return shape ('a score and a priority-ordered fix list'), which matters since no output schema exists. Minor internal friction: it says it fetches 'one public web page' yet also checks robots.txt and sitemap, which are separate requests.

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?

Front-loaded with the action, then a dense but purposeful checklist, then the return value. The only wasted phrase is 'Only reads the page,' which restates readOnlyHint already present in annotations.

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?

With five parameters at full schema coverage and no output schema, the definition covers what the agent needs: what is checked, what comes back, and that it is a read. The only loose end is that robots.txt and sitemap checks imply additional network targets beyond the single page the description promises.

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%, so the baseline is 3. The description earns a point above baseline by explaining why the optional identity parameters exist: 'name and phone matching the Google profile' and 'title and H1 naming the service and area' map directly to phone, business_name, main_service and suburb, giving meaning the schema's short field notes don't.

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?

Opens with a specific verb and resource ('Fetches one public web page and checks its local SEO layer') and enumerates the concrete checks performed. The website-page scope cleanly separates it from sibling tools like audit_gbp_profile, which audits the Google Business Profile rather than a page.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the schema note 'usually the homepage or the page the Google profile links to' hints at the scenario, but the description itself never states when to pick this over audit_gbp_profile, get_free_expert_audit, or the individual check_* tools. An agent must infer the choice from the resource type alone.

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.