Skip to main content
Glama
Sign In

CallAI SEO

by com.callaiapi
OverviewDiscussionsAdmin

Google SERP

google_serp
Read-only

Live Google organic search results for a keyword in a given country and language: ranks, titles, URLs, snippets, plus the AI Overview text and the sources it cites. Billed per call (about $0.002 for depth 10).

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": {
      "keyword": "<keyword>"
    },
    "name": "google_serp"
  }
}

Input Schema

NameRequiredDescriptionDefault
depthNoNumber of results to fetch, 10–100 (default 10). Cost grows with depth.
deviceNoDefault desktop.
keywordYesSearch query. Supports operators such as site:example.com.
language_codeNoLanguage code, e.g. en (default), de, fr, ja, es, pt, zh-CN.
location_codeNoDataForSEO location code. 2840 = United States (default), 2826 = UK, 2276 = Germany, 2250 = France, 2392 = Japan, 2356 = India, 2076 = Brazil.

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 already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context: results are 'live', they include AI Overview text and its cited sources, and the call is billed (~$0.002 at depth 10) — a cost trait no annotation conveys.

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, zero waste. The output inventory comes first so an agent knows what it gets, and the billing note is a short, load-bearing second sentence that front-loads the cost consideration.

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 five parameters, one required, no output schema and no nested objects, the description supplies what is missing: the shape of the response (ranks, titles, URLs, snippets, AI Overview) and the cost model. Combined with annotations that cover read-only/open-world semantics, an agent has enough to call it 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 (depth, device, keyword, language_code, location_code) is already documented with examples and enums. The description only reinforces two of them in prose ('keyword in a given country and language'), adding little meaning beyond the schema; 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?

The description names a specific verb and resource ('Live Google organic search results for a keyword') and enumerates the returned fields (ranks, titles, URLs, snippets, AI Overview text and cited sources). The word 'Google' plus the sibling 'bing_serp' makes the engine distinction obvious, though it never explicitly contrasts the two.

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 only implied: it is a search query tool for a keyword, country and language. There is no explicit when-to-use guidance against the many siblings that also take a keyword (keyword_overview, keyword_ideas, ranked_keywords, bing_serp), and no statement of when NOT to use it or when a cheaper alternative is preferable.

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

All CallAI SEO 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