Skip to main content
Glama

rankparse-mcp

by io.github.abhibavishi
OverviewDiscussionsAdmin

get_gsc_low_ctr_queries

Read-onlyIdempotent

Find search queries with high impressions but low CTR. These are ranking but not getting clicked, usually because the title or meta description is weak or misleading. Fixing these is typically higher ROI than chasing new rankings. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it. When several Google accounts are connected, the property is read through the account that can see it.

Input Schema

NameRequiredDescriptionDefault
siteYesProperty URL e.g. "https://example.com"
maxCtrNoOnly include queries with CTR at or below this value 0–1 (default 0.05 = 5%)
endDateYesEnd date YYYY-MM-DD
rowLimitNoMax rows (default 50, max 1000)
startDateYesStart date YYYY-MM-DD
searchTypeNoSearch type (default web). Google does not offer every dimension for discover and googleNews (query is not available there).
minImpressionsNoOnly include queries with at least this many impressions (default 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / searchType
      Added value: +{
+  "description": "Search type (default web). Google does not offer every dimension for discover and googleNews (query is not available there).",
+  "enum": [
+    "web",
+    "image",
+    "video",
+    "news",
+    "googleNews",
+    "discover"
+  ],
+  "type": "string"
+}
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world behavior. The description adds genuinely non-structured operational context: GSC must be connected, where to send the user to connect it, and how multi-account property resolution works.

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?

Four short sentences, front-loaded with what the tool finds and why it matters; each sentence contributes either interpretation or setup guidance. No repetition of schema or annotation content.

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?

Covers the key non-schema prerequisites (connection, integration URL, account selection) for a read-only tool with a fully described schema. Since there is no output schema, a brief note on what a row contains would have completed it.

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%, including defaults for maxCtr, minImpressions, and rowLimit, so the schema carries parameter semantics. The description adds no threshold detail or format hints beyond the schema, 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 ('Find search queries with high impressions but low CTR') and explains the interpretation (ranking but not clicked). It implicitly separates itself from get_gsc_low_ctr_pages by targeting queries rather than pages, but never names that sibling explicitly.

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?

Gives clear diagnostic context ('title or meta description is weak') and a strategic rationale for using it, which implies when it is useful. However, with ~40 GSC siblings including get_gsc_opportunity_queries and get_gsc_low_ctr_pages, it offers no explicit alternative or exclusion guidance.

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

All rankparse-mcp 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