Skip to main content
Glama

rankparse-mcp

by io.github.abhibavishi
OverviewDiscussionsAdmin

get_gsc_page_trend

Read-onlyIdempotent

Get daily click/impression/CTR/position trend for a specific page. Use this to see how a single page's search performance has changed over time, useful for measuring the impact of a content update or spotting a ranking drop. 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
pageYesFull page URL e.g. "https://example.com/blog/post"
siteYesProperty URL e.g. "https://example.com"
endDateYesEnd date YYYY-MM-DD
startDateYesStart date YYYY-MM-DD
searchTypeNoSearch type (default web). Google does not offer every dimension for discover and googleNews (query is not available there).

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

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds real context beyond them: Google Search Console must be connected, the user must be directed to an integration URL, and multi-account property resolution is handled automatically.

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 sentences, front-loaded with the returned metrics and followed by use cases and the auth prerequisite. No sentence is filler.

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 a read-only, non-destructive trend query with full schema coverage and annotations, the description covers what is returned, why to use it, and the critical connection prerequisite. The lack of an output schema is offset by the metric list, though the granularity of the daily series is only implied.

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 the schema already documents site, page, startDate, endDate, and searchType. The description does not add syntax, formatting, or selection guidance beyond what the schema provides.

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: daily click/impression/CTR/position trend for a specific page. The 'single page' framing distinguishes it from site-wide trend siblings like get_gsc_date_trends, but it does not explicitly name competing tools such as get_gsc_query_trend or get_gsc_top_pages.

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

Usage Guidelines4/5

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

Gives clear when-to-use context: measuring the impact of a content update or spotting a ranking drop for one page. It stops short of explicit exclusions or naming the alternative tools to use for query-level or site-level trends.

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