Skip to main content
Glama

Google Business Profile & Local SEO Checker

List a site's service and area pages

list_site_services
Read-onlyIdempotent

Reads the website's sitemap (or its homepage links if there is no sitemap) and returns the service pages and suburb/area pages it has. Use it to work out which Services belong on the Google profile and whether the service area on the profile matches the suburbs the site actually covers.

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": {
      "website": "<website>"
    },
    "name": "list_site_services"
  }
}

Input Schema

NameRequiredDescriptionDefault
websiteYesThe business's website

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior the annotations cannot convey: it discloses the sitemap-first strategy with a homepage-link fallback when no sitemap exists. It stops short of saying what happens on an unreachable site, empty sitemap, or how many pages are returned.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, the mechanism and its fallback are front-loaded in the first, and the second is purely the use case. No filler or redundant restatement of the tool name.

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 one-parameter read tool with no output schema, the description is nearly complete: it describes the input source, the fallback, and the shape of the result (service pages plus suburb/area pages). Missing only edge-case behavior for sites with no sitemap and no usable homepage links.

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?

There is a single required parameter with 100% schema description coverage, so the schema already carries the semantics and a baseline of 3 applies. The description does not clarify whether the website value should include a scheme, trailing slash, or path, so it adds no meaning beyond the schema.

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 (reads) and resource (sitemap/homepage links) and names the exact output categories (service pages and suburb/area pages). It is precise enough for an agent to know what comes back, though it never contrasts itself with a nearby crawl-type sibling such as audit_website_local_seo, so differentiation relies on the agent's own knowledge.

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 a concrete downstream purpose: deciding which Services belong on the Google profile and whether the profile's service area matches the suburbs the site covers. That is clear when-to-use context, but there is no explicit exclusion or statement of when another tool (e.g. a full site audit) would be the better call.

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.