Keytomic

Get search performance

get_search_performance

Read-only

A short Search Console performance overview: clicks, impressions, CTR and average position for a period and its comparison period, the change in each, a daily series for both, and the top queries and pages by clicks. Data comes from the site’s connected Google Search Console property, web search only. By default the period is the last 28 days that have final data, which usually ends 2 to 3 days ago, and it is compared with the 28 days before it. Search Console does not separate AI Overviews or AI Mode traffic from web search. Totals come from the whole property with no filter, so anonymized queries are counted; the top query list leaves out search-operator queries by default. Position has no change when either period had no impressions.

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": {
      "projectId": "<projectId>"
    },
    "name": "get_search_performance"
  }
}

Input Schema

Name	Required	Description	Default
`rowCap`	No	Most rows to read from Google for each query or page list; default 50,000, at most 200,000. The result says truncated when the cap stopped a read.
`endDate`	No	Last day, YYYY-MM-DD. Defaults to the last day with final data. A later day reads data Google still collects, and the result says so.
`topLimit`	No	Rows in each top list. Default 10.
`projectId`	Yes	Site to act on, from list_sites. Only its connected Search Console property is used.
`startDate`	No	First day, YYYY-MM-DD. Defaults to 28 days ending on endDate.
`compareWith`	No	"previous": the period of equal length just before. "sameLastYear": the same dates one year earlier, for seasonal sites.	previous
`includeSearchOperatorQueries`	No	Keep queries with a search operator, such as site:, inurl:, intitle:, filetype: or before:, in the lists. Totals always include them.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered, and the description adds genuine operational context: final-data lag, that AI Overviews/AI Mode traffic is not separable, that unfiltered totals include anonymized queries, and that position deltas are suppressed when either period has no impressions. The remaining gap is return-size/pagination behavior, though rowCap and truncated flags are documented in the schema.

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?

Three sentences, front-loaded with the metric list and then the caveats, with essentially no filler; every clause carries information. The opening sentence is packed — a metric enumeration, a comparison, a series, and two top lists in one breath — which costs a little readability but not correctness.

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?

With no output schema, the description must convey what comes back, and it does: totals, deltas, daily series, top queries and pages, plus truncation-relevant rowCap semantics. For a 7-parameter read tool whose annotations already cover safety, an agent has everything needed to call it and interpret results correctly.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds meaning the schema does not: the default period relationship (28 days ending on endDate, compared with the 28 days before), and the fact that totals always include search-operator queries even when the top lists exclude them. The sameLastYear seasonal rationale is echoed from the schema rather than added, but the cross-parameter interactions are real value.

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 names a specific resource and enumerates the exact payload: clicks, impressions, CTR, average position, both periods and their deltas, a daily series, and top queries/pages by clicks. It also pins the source (the site's connected Google Search Console property, web search only), which lets an agent separate it from get_analytics_performance or search_analytics_query without opening a schema.

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 description thoroughly explains defaults and edge behavior (28-day window ending 2-3 days ago, previous-period comparison) but never states when to choose this over sibling tools such as get_search_insight or search_analytics_query. Usage is implied by the 'overview' framing rather than stated as a routing rule.

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

All Keytomic 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?