Skip to main content
Glama

Visibility Genies

Read Search Console performance

get_search_console_performance
Read-only

Reads the project's Google Search Console search analytics: clicks, impressions, CTR and average position, grouped by query, page, country, device, date or search appearance, with filters, paging and a comparison with an earlier period. Needs Search Console connected to the project. Uses no credits.

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_console_performance"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoWhich Google search to report on. Defaults to web.
brandNo'branded' keeps only searches that name the project's brand, 'nonBranded' only those that do not, matched by a simple pattern of the saved brand names (the domain's name when none are saved). Default all. Google leaves rare searches out when filtering by search term, so branded plus nonBranded can be less than all.
compareNoAlso read the period of the same length just before ('previous') or the same days a year before ('year'), and give each row its numbers there as `previous`. A row not among the first 1,000 rows of that period has previous null. One more Search Console read.
endDateNoLast day, YYYY-MM-DD in Pacific Time. Give it with startDate.
filtersNoUp to 5 filters, all of which a row must match.
rowLimitNoRows to return, at most 1000. Defaults to 1000. Page through more with startRow.
startRowNoRows to skip, for paging. Defaults to 0.
dataStateNo'all' includes the newest, still changing days; 'final' only settled data. Defaults to all.
dateRangeNoA date window ending at the latest data. Defaults to last_28_days. Ignored when startDate and endDate are given.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.
startDateNoFirst day, YYYY-MM-DD in Pacific Time. Give it with endDate.
dimensionsNoWhat to group rows by, 1-4 of the options. Defaults to ["query"]. searchAppearance cannot be combined with another dimension.

Output Schema

NameRequiredDescriptionDefault
okYes
metaNo
rowsNo
reasonNo
endDateNo
hasMoreNo
siteUrlNo
comparedNo
rowCountNo
connectedNo
startDateNo
connectUrlNo
dimensionsNo
nextStartRowNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the connection requirement, that the call consumes no credits, and (in schema text) that comparison mode costs one extra Search Console read. What it omits is any mention of the 1,000-row ceiling's effect on results, which matters for large accounts.

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, front-loaded with the resource and metrics, then prerequisites and cost. Nothing is repeated and no filler or marketing language appears; every clause carries information an agent needs.

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 an output schema present, the description needn't explain return values, and it covers the resource, metrics, prerequisites and cost adequately for a 12-parameter read tool. The only shortfall is that it doesn't hint at large-result handling or failure modes when Search Console is not connected, which would help an agent recover from errors.

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 explains every one of the 12 parameters, including the nuanced brand, compare and dataState semantics. The description only restates the concept of grouping, filtering, paging and period comparison, adding no syntax or edge-case detail beyond the schema; baseline 3 applies.

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?

States a specific verb and resource ("Reads ... Google Search Console search analytics") and enumerates the exact metrics returned: clicks, impressions, CTR and average position. The grouping options and the sitemaps sibling make the scope unambiguous, so an agent can tell this apart from get_search_console_sitemaps without opening the 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 gives a hard prerequisite ("Needs Search Console connected to the project") and a cost signal ("Uses no credits"), which helps an agent prefer this over credit-consuming reads. However, it never says when to use this instead of adjacent tools such as get_search_opportunities or the Google Analytics performance siblings, so selection guidance is only implied.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources