Skip to main content
Glama
Sign In

Variafy

by com.variafy
OverviewDiscussionsAdmin

Read Search Console data

search_console_read
Read-onlyIdempotent

Reads connected Search Console sites: clicks, impressions, CTR and position in Google Search by query, page, country and device. action "list_tools" lists every operation of this router with its field names (get_tool_schema returns the input schema); it does not call Google and is free. action "execute" runs one read: {"action":"execute","tool_name":"search_console_performance","arguments":{}}. Reads:

  • search_console_performance: Google Search performance of the connected Search Console site: clicks, impressions, CTR and average position by query, page, country, device, date or search appearance, with the site totals for the period.

  • search_console_paid_organic: Compares Google Search results of the connected site with the search terms of a connected Google Ads account: terms Google Ads pays for where the site already ranks in the top 3, searches on page 2 and lower with no ads, and terms that convert in Google Ads where the site is not visible organically.

  • search_console_indexing: Indexing state of pages as Google sees them: whether the page is indexed, which address Google picked as canonical, whether robots.txt or a noindex tag blocks it, when Google last crawled it and whether the fetch succeeded.

  • search_console_opportunities: Where Google Search is close to paying off: pages or queries sitting just off the first page, ones shown often but rarely clicked, and ones that lost position against the previous period. Read-only and free: changes nothing and does not count toward the monthly change limit. Google Analytics and Search Console have their own request quotas; they do not use this server’s Google Ads API quota.

Input Schema

NameRequiredDescriptionDefault
actionYeslist_tools: every operation with its field names, flags and router. execute: run the read named by tool_name.
argumentsNoFor execute: the fields of the operation, plus "connection" when several Search Console sites are connected. Omit or {} when it has none.
tool_nameNoFor execute: the operation name from list_tools, e.g. search_console_performance.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds valuable context beyond them: it is free, does not consume the monthly change limit, and uses separate quota pools from the Google Ads API. It does not cover pagination or response shape, but no output schema exists so that is less critical.

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?

Front-loads the tool's purpose and action mechanics, then presents each sub-operation as a structured bullet. Slightly verbose and mildly redundant with annotations on the read-only point, but for a four-operation router the detail is largely justified and easy to scan.

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?

Covers purpose, router mechanics, all four sub-operations, parameter usage via the execute example, and cost/quota behavior. With annotations handling safety and no output schema to explain, an agent has everything needed to select and invoke it 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 description coverage is 100%, so baseline is 3. The description enumerates four valid tool_name values with rich explanations of what each read returns, going beyond the schema's single example and helping the agent choose the right operation. Semantics for action and arguments remain delegated to the schema.

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 (reads) and resource (connected Search Console sites) with exact metrics, and differentiates from siblings by naming get_tool_schema and clarifying the distinct role of list_tools versus get_tool_schema. It also separates its quota from the Google Ads API quota, making its scope unmistakable.

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?

Explains the two router actions and when to use each: list_tools is free discovery with field names, execute runs one read with a concrete example. Lacks explicit when-not guidance or direct contrast with other read tools like google_analytics_read.

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

All Variafy 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