Skip to main content
Glama

Google Business Profile & Local SEO Checker

Find the Google profile from the website

find_google_profile
Read-onlyIdempotent

Reads a business's website and pulls out every link to its Google Business Profile, with the Place ID or CID where the link carries one. Use this instead of asking the user to go and find their listing. If the site links to no profile at all, that is itself a finding worth reporting.

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

Input Schema

NameRequiredDescriptionDefault
websiteYesThe business's website

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely new context: it performs live external fetching, may yield zero results, and an empty result is meaningful rather than an error. Return shape is only loosely sketched (a set of links plus IDs).

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?

Three short sentences, front-loaded with the core action, then the usage directive, then the edge case. No filler or restatement of the 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?

With no output schema, the description carries the burden of describing returns, and it does so at a high level (links plus Place ID/CID). It leaves the concrete result structure (fields, one-vs-many entries, error behavior on unreachable sites) unspecified.

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% for the single parameter, so the schema already documents 'website'. The description adds no format detail (scheme, trailing path, subdomain handling) beyond the schema, which is the baseline 3 case.

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?

States a specific verb ('Reads') and resource ('a business's website') and a precise output ('every link to its Google Business Profile, with the Place ID or CID'). This clearly separates it from siblings like audit_gbp_profile, which operate on the profile rather than the site.

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 an explicit use case ('Use this instead of asking the user to go and find their listing') and guidance for the null-result case ('If the site links to no profile at all, that is itself a finding worth reporting'). It does not name a sibling alternative or exclusion, so it stops short of a 5.

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.