Skip to main content
Glama

Visibility Genies

Get local search results

get_local_serp_results

Fetches a Google Maps or Local Finder results page from a coordinate, with the rows trimmed to identity, rank, rating, categories and hours. Decide yourself how to match a target business in the rows. Estimated price: $0.01 for a Google Maps search at any depth; Local Finder bills the same for each page of 20 places on desktop, 10 on mobile. 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>",
      "keyword": "<keyword>",
      "near": "<near>"
    },
    "name": "get_local_serp_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
nearYesThe point the results are fetched from.
depthNoPlaces to fetch. Defaults to 20.
deviceNoDefaults to mobile.
keywordYes
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
searchTypeNoDefaults to maps.
languageCodeNoLanguage code such as en, es or vi. When left out, the language of the project's default market is used (see list_projects).
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
resultsYes
savedResultIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, openWorldHint=true and destructiveHint=false; the description goes far beyond that with per-call pricing ($0.01, per-page billing for Local Finder at 20 desktop/10 mobile), the workspace agent spend limit ceiling, the hold-plus-margin mechanism, and the pre-purchase refusal path. This is exactly the billing and authorization context annotations cannot express, though it does not mention rate limits or failure/retry semantics.

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?

Well front-loaded: purpose and returned fields first, then cost, then the approval escalation path. The cost paragraph is dense and slightly run-on ('it holds at most its estimate plus a margin while it runs and is charged what it bought, never more'), but nearly every sentence carries actionable information.

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?

For an 8-parameter, nested-object, open-world paid call with an output schema, the description covers what is bought, what it costs, what the spend ceiling does, and how to recover from a refusal. Nothing an agent needs in order to call it correctly or safely appears to be missing.

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 88%, so baseline is 3, and the description adds real meaning beyond it: depth drives Local Finder page-based billing, device changes the page size (20 vs 10), and approvedMaxCostUsd is only set after a refusal and only with user approval. It does not clarify the zoom or languageCode semantics beyond what the schema already says.

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?

Opens with a specific verb and resource: 'Fetches a Google Maps or Local Finder results page from a coordinate,' and even states the trimmed fields returned (identity, rank, rating, categories, hours). It implicitly separates itself from the plain organic SERP tool by naming Maps/Local Finder surfaces, but it never names a sibling outright, so sibling routing is left to inference.

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 implied by 'Decide yourself how to match a target business in the rows' and by the detailed spend-limit/approval workflow, which does tell the agent what to do when a call is refused. However, with siblings like get_serp_results and search_local_businesses present, it gives no explicit when-to-use-this-vs-alternative guidance, leaving surface selection to the reader.

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