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

NameRequiredDescriptionDefault
qYesSearch query to track rankings for. Required.
glNoCountry code (e.g., 'us', 'gb'). Defaults to the country of location, or of latitude and longitude, when that country can be identified, and to us otherwise.
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. Changed1 schema field changed
    • changedInput schema / properties / gl / description
      Previous value: -"Country code (e.g., 'us', 'gb'). Default: us."New value: +"Country code (e.g., 'us', 'gb'). Defaults to the country of location, or of latitude and longitude, when that country can be identified, and to us otherwise."
  2. 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"
+}
  3. Changed1 schema field changed
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
  4. 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"
+]
  5. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnly, non-destructive, open-world), so the bar is lower. The description adds genuinely useful context not covered there: the 100-result cap per request and the returned fields (position, title, URL, snippet), which matters because no output schema exists.

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 tight sentences with zero redundancy: purpose first, then return shape, then use case. Nothing could be removed without losing information.

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 an 8-parameter read-only search tool with no output schema, the description covers purpose, return fields, and result limit sufficiently. It omits any localization/geotargeting nuance (latitude/longitude vs location), but the schema handles those constraints fully.

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 all eight parameters are already documented with defaults, ranges, and mutual exclusions. The description only echoes the 'up to 100 results' cap tied to num, adding no new syntax or format meaning, so baseline 3 applies.

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?

States a specific verb and resource ('Get Google organic search results') and frames the intent ('for SEO rank tracking'), which is unambiguous. It does not differentiate itself from near-identical siblings like google_search_light or bing_search, so it stops short of a 5.

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?

'Ideal for monitoring keyword rankings and SERP analysis' implies when the tool is appropriate but offers no explicit when-not guidance and names no alternative. With several sibling search tools available, the agent must infer the routing decision itself.

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
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources