Skip to main content
Glama

Business Profile: find category and service-area ids

gbp_find_options
Read-onlyIdempotent

Look up Google's own ids for a Business Profile edit: kind 'category' searches Google's category list by name (e.g. 'fence'), kind 'service_area' finds a city, ZIP or county (e.g. 'Hillsboro, OR'). gbp_update_profile takes only ids from here, never free text.

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": {
      "gbp_location_id": "<gbp_location_id>",
      "kind": "<kind>",
      "query": "<query>"
    },
    "name": "gbp_find_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes
queryYesA category word, or a city/ZIP/county with its state
gbp_location_idYesFrom gbp_list_locations

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), and the description adds value beyond them by saying the output is Google's own ids rather than human-readable names, and that each 'kind' searches a different Google-maintained namespace. It does not address ambiguous or multiple matches, which matters for a free-text open-world lookup, keeping it off 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.

Conciseness5/5

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

Two sentences, front-loaded with the core purpose, then the per-kind examples, then the downstream constraint. Every clause carries information; no filler or repetition of the title.

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 three required params and no output schema, the description supplies the crucial missing piece by stating that results are Google ids consumed by gbp_update_profile. It could be fuller about lookup-result behavior (multiple matches, no-match cases), but nothing essential for calling it correctly is absent.

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 67% and the one undescribed property (kind) is the one the description clarifies most, explaining that 'category' searches Google's category list and 'service_area' resolves a city, ZIP or county. The examples and the 'with its state' phrasing also flesh out what the query string should look like, adding meaning beyond the schema's min/maxLength constraints.

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?

"Look up Google's own ids for a Business Profile edit" states a specific verb and resource, then enumerates the two lookup modes ('category' vs 'service_area') with concrete examples ('fence', 'Hillsboro, OR'). It also names its consumer, gbp_update_profile, which separates it from the other gbp_* siblings that read or write profiles.

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 description makes the usage path explicit: this tool produces ids and gbp_update_profile accepts only ids from here, never free text, so an agent knows this lookup is a required precursor to profile edits. It stops short of any when-not-to-use statement or note about which sibling to pick for other lookups, so it is clear context without full exclusions.

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.