Skip to main content
Glama

Searchapi

by io.searchapi
OverviewDiscussionsAdmin

Google Rank Tracking

google_rank_tracking
Read-only

Get Google organic search results for SEO rank tracking. Returns up to 100 results per request with position, title, URL, and snippet. Ideal for monitoring keyword rankings and SERP analysis.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query to track rankings for. Required.
glNoCountry code (e.g., 'us', 'gb'). Default: us.
numNoNumber of results (1-100). Default: 100.
pageNoPage number (1-10). Default: 1.
safeNoSafeSearch filtering level. Default: blur.
latitudeNoLatitude of the search location, in decimal degrees (-90 to 90). Use with `longitude`. Cannot be combined with `location`.
locationNoGeographic location for localized rankings (e.g., 'New York, NY').
longitudeNoLongitude of the search location, in decimal degrees (-180 to 180). Use with `latitude`. Cannot be combined with `location`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / latitude
      Added value: +{
+  "description": "Latitude of the search location, in decimal degrees (-90 to 90). Use with `longitude`. Cannot be combined with `location`.",
+  "type": "number"
+}
    • addedInput schema / properties / longitude
      Added value: +{
+  "description": "Longitude of the search location, in decimal degrees (-180 to 180). Use with `latitude`. Cannot be combined with `location`.",
+  "type": "number"
+}
  2. Changed1 schema field changed
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
  3. Changed2 schema fields changed
    • changedInput schema / properties / safe / description
      Previous value: -"Safe search setting."New value: +"SafeSearch filtering level. Default: blur."
    • changedInput schema / properties / safe / enum
      Previous value: -[
-  "active",
-  "off"
-]New value: +[
+  "active",
+  "blur",
+  "off"
+]
  4. First observed

TDQS

A3.8/5.0
Behavior3/5

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

The annotations already establish it as read-only and non-destructive, so the description only needs to add extra behavioral context. It does add output shape and result-count, yet it does not mention rate limits, pagination trade-offs, or how location and geolocation parameters affect rankings. This is adequate but not deeply transparent.

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?

The description is only two sentences, front-loads the action and resource, and adds only relevant output/use-case details. It is concise without sacrificing clarity.

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 read-only search tool with full schema coverage, the description provides enough to understand what results look like and why to use the tool. It could expand on practical quirks like location-based differences or pagination behavior, but those are mostly inferable from the schema and the tool's stated purpose.

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 description coverage is 100%, so the description does not need to document every parameter. The one added semantic is that results include position/title/URL/snippet, which helps understand what the output means, but it does not enrich understanding of any individual parameter. Baseline of 3 is appropriate.

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?

The description clearly says 'Get Google organic search results for SEO rank tracking' and lists returned fields (position, title, URL, snippet), which makes the tool's purpose specific. It does not explicitly compare to sibling tools such as google_search_light, but the SEO/rank-tracking framing differentiates it enough.

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?

It offers a clear use case ('Ideal for monitoring keyword rankings and SERP analysis') but never names alternatives or explicitly states when not to use it. The intended context is clear, though exclusion guidance and sibling pointers are missing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Searchapi toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources