Ranksmile

Search Console performance

gsc__performance

Read-onlyIdempotent

The last 30 days of Google Search Console for this workspace's site: clicks, impressions, CTR (%) and average position per query or per page, most clicks first. Pages or queries with many impressions at position 8-20 are the quickest wins.

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": {
      "workspace_id": "<workspace_id>"
    },
    "name": "gsc__performance"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Max rows, 1-100 (default 50).
`offset`	No	Rows to skip (default 0). Keep paging while has_more is true.
`group_by`	No	Default query.
`workspace_id`	Yes	From workspace__list.

Output Schema

Name	Required	Description
`rows`	Yes	key (query or page path), clicks, impressions, ctr (%), position.
`domain`	Yes
`totals`	Yes
`group_by`	No
`has_more`	Yes
`connected`	Yes
`last_fetched`	No
`workspace_id`	Yes
`last_fetch_error`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world, non-destructive behavior, so the bar is lower. The description still adds real behavioral facts the annotations don't: a fixed 30-day window with no date-range control, and results ordered most-clicks-first. Pagination is left to the schema and output schema.

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, metrics and window front-loaded, and the second sentence is an actionable interpretation tip rather than filler. Nothing to trim.

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?

With annotations covering safety, a 100%-covered schema, and an output schema, the description supplies what structured fields cannot: scope, fixed time window, sort order, and a prioritization heuristic. Only a note on data freshness/property scoping is missing, which is minor.

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 the baseline is 3. The description reinforces the group_by choice by stating results come "per query or per page," but adds no syntax, limits, or paging detail beyond what the schema already documents for limit, offset, and workspace_id.

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?

Names the exact resource (Google Search Console for this workspace's site), the fixed window (last 30 days), all four metrics (clicks, impressions, CTR %, average position), and the two grouping dimensions. This is unambiguous against siblings like visibility__overview or audit__overview, which are not GSC search-analytics reports.

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?

The closing sentence ("impressions at position 8-20 are the quickest wins") hints at the analysis use case, but there is no explicit statement of when to pick this over visibility__overview or rank__keywords, and no exclusions. Usage is only implied.

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

All Ranksmile tools Inspect

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

Need Help?