Skip to main content
Glama
Sign In

Crawlwise

by site.crawlwise
OverviewDiscussionsAdmin

Get query gaps for a page

get_query_gaps
Read-onlyIdempotent

For one page of a site: the search queries it already earns impressions for in Google Search Console and Bing Webmaster Tools (merged, grouped into clusters of close variants), whether the page covers each cluster well, weakly or not at all (with the heading or sentence that covers it), a High/Medium/Low priority, and a suggested change. Spends no credits. Needs Search Console and/or Bing connected on the site page. Does NOT write the new copy and does NOT read the live SERP: hand the returned brief to the writer, and check the top results yourself before adding a section. An empty cluster list means no query rows were reported, not that the page has no demand.

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": {
      "site_id": "<site_id>",
      "url": "<url>"
    },
    "name": "get_query_gaps"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFull URL of a page on that site.
rangeNoDays of query data. Default 90.
site_idYesA site id from list_sites.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly, idempotent, non-destructive annotations, the description adds operationally important behavior: zero credit cost, required integrations, no copying output, no live SERP lookup, and the meaning of an empty cluster list. Those details materially change how an agent should use and report the result.

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 definition is dense but front-loaded: purpose, output composition, constraints, and interpretation guidance come in quick succession with no filler. Every sentence adds a distinct operational fact.

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 a read-only analysis tool with no output schema, the description is complete enough to call correctly: it names required integrations, describes the returned brief in detail, sets scope limits, and explains the empty-result edge case. Nothing essential for invocation or interpretation is missing.

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% and each parameter is already documented with type, enum, and default, so the schema carries parameter meaning. The description adds context that the URL is a page on the site and that data comes from search-console sources, but it does not explain the 28/90-day range or site_id beyond what the schema already says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: it returns search queries a page already earns impressions for, merged across Google Search Console and Bing, grouped into clusters, with coverage assessment, priority, and a suggested change. That is far more specific than the title and clearly distinguishes it from audit-oriented siblings like audit_page or get_crawl_issues.

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

Usage Guidelines5/5

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

It gives explicit preconditions (Search Console and/or Bing must be connected), states it costs no credits, and draws hard boundaries: it does not write copy and does not read the live SERP, so the agent must hand results to a writer and check top results separately. It also explains how to interpret an empty result set rather than leaving the agent to guess.

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

All Crawlwise toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources