Skip to main content
Glama

Visibility Genies

Get a business profile

get_business_profile

Reads one business's Google Business Profile: category, rating and its breakdown, address, phone, website, whether it is claimed, opening hours, photo count and Google's cid and place_id. Name the business with exactly one of businessName, cid or placeId; use near when a name is ambiguous. Estimated price: $0.02 per profile; a profile bought within a day, here or on the Local page, is answered at no charge. Each call may spend up to the workspace's agent spend limit ($2.00 unless changed in Settings) without asking: it holds at most its estimate plus a margin while it runs and is charged what it bought, never more. A call whose maximum is above the limit is refused before anything is bought, with its estimate and maximum: ask the user, then call again with approvedMaxCostUsd set to the amount they approved.

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": {
      "projectId": "<projectId>"
    },
    "name": "get_business_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
cidNoGoogle-defined business CID (from get_local_serp_results rows). Most precise identifier.
nearNoCoordinate to search from. Use it when the business name is ambiguous; otherwise locationCode is enough.
placeIdNoGoogle Maps place_id (from get_local_serp_results rows).
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
businessNameNoBusiness name as it appears on Google. Supply exactly one of businessName, cid, or placeId.
languageCodeNoLanguage code such as en, es or vi. When left out, the language of the project's default market is used (see list_projects).
locationCodeNoLocation code. Ignored when `near` is set; otherwise defaults to the project's market.
approvedMaxCostUsdNoThe most, in USD, the user approved for this call after seeing its estimate and maximum. Only needed after a call was refused for costing more than the workspace's agent spend limit; never set it without asking the user.

Output Schema

NameRequiredDescriptionDefault
costNo
metaNo
profileYes
savedResultIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare openWorldHint=true, destructiveHint=false and notably readOnlyHint=false; the description explains why a read carries a side effect by disclosing the $0.02 per-profile charge, the 24-hour free-repeat window, and the workspace spend-limit hold/refuse semantics. What it does not cover is the authorization scope needed or latency of a profile fetch, so it stops short of 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?

Front-loaded with what is returned, then identifier rules, then billing behavior — a sensible order with no filler. The billing paragraph is dense (three sentences on estimate, hold, margin and refusal) and could be tightened, which keeps it from a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, the description need not explain return shape, yet it still lists the key fields for selection purposes. Pricing, spend-limit behavior, refusal handling and the identifier disambiguation rules together cover everything an agent needs to call this 8-parameter, nested-object tool correctly.

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%, so every parameter already carries its own description, and the description's 'exactly one of businessName, cid or placeId' and the approvedMaxCostUsd retry rule largely restate those schema texts. It adds the interaction constraint between identifiers but no syntax or format detail beyond the schema, so baseline 3 applies.

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 and resource ('Reads one business's Google Business Profile') and enumerates the returned attributes (category, rating breakdown, address, phone, website, claimed status, hours, photo count, cid, place_id). This clearly separates it from siblings like get_business_reviews and get_business_updates, which cover different slices of the same business.

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

Usage Guidelines5/5

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

Gives explicit identification rules: exactly one of businessName, cid or placeId, with `near` as the disambiguator when a name is ambiguous. It also defines the escalation path when a call exceeds the workspace spend limit — ask the user, then retry with approvedMaxCostUsd — which is guidance an agent could not infer on its own.

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