Skip to main content
Glama

check_google_serp

Read-only

Fetches live top 10 Google search results and People Also Ask.

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": "check_google_serp"
  }
}

Input Schema

NameRequiredDescriptionDefault
countryNous
keywordYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuine behavioral detail beyond that: results are 'live' (real-time fetch) and the returned set is capped at top 10 plus People Also Ask. It omits latency/cost implications of a live SERP fetch and says nothing about how results vary by country.

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?

A single front-loaded sentence with no filler, and the key facts (live, top 10, PAA) come first. It is arguably too terse for a tool with an undocumented country parameter, but there is no wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a low-complexity two-parameter tool with no output schema, the description conveys roughly what comes back (top 10 organic results and PAA). However, it leaves the country parameter and the keyword format unexplained, and does not note that a live fetch may be slower or rate-limited, so the definition is workable but incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the burden, and it does not: the 'country' parameter (default 'us') is never mentioned, and 'keyword' is only implied by 'Google search results' with no statement of expected format. The agent gets no guidance on how to scope the query by locale.

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?

Names a specific verb ('Fetches') and a specific resource ('live top 10 Google search results and People Also Ask'), which is clearly distinct from the sibling tools focused on rankings, robots/sitemaps, and on-page audits. It stops short of explicitly contrasting itself with any sibling, but the resource is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use or when-not-to-use guidance and no named alternative. An agent must infer from the phrase 'live top 10 Google search results' that this is the SERP-scraping option rather than the ranking-tracking sibling, which is left entirely to inference.

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