Skip to main content
Glama
Sign In
flin-google-search-console-mcp

flin-google-search-console-mcp

by flin-agency
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

get_top_queries

Read-onlyIdempotent

Retrieve top search queries for a Google Search Console property within a date range to identify which terms drive impressions and clicks.

Instructions

Get top query rows for a property over a date range.

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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "get_top_queries"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo
filtersNo
end_dateYes
site_urlNo
row_limitNo
start_rowNo
data_stateNo
start_dateYes
search_typeNoweb

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.7
    • addedInput schema / properties / account
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Account"
+}
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

The annotations establish a safe, idempotent read, while the description adds only basic property and date-range scoping. It does not explain what makes a query 'top,' how results are ordered, or how filtering and pagination affect the retrieval.

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?

The single sentence is front-loaded, readable, and free of filler. Its brevity is efficient, although some additional detail is needed elsewhere to make the tool reliably invocable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema and safety annotations reduce some documentation burden, but the description is insufficient for a nine-parameter tool whose schema provides no parameter descriptions. Missing ranking semantics, filter structure, property-selection rules, pagination behavior, and sibling routing are material gaps.

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

Parameters2/5

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

The description loosely supports the date parameters and property selection, but does not specify date formats or distinguish account from site_url. With 0% schema description coverage, filters, row_limit, start_row, data_state, and search_type remain effectively undocumented.

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?

The description uses a clear verb and resource—getting top query rows—and adds property and date-range scope. It implies a distinction from get_top_pages by focusing on queries, but does not explicitly differentiate itself from query_performance or get_dimension_breakdown.

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 wording implies use when an agent wants query-level results for one property and period. It gives no explicit selection criteria, prerequisites, or guidance on when to use a sibling tool instead.

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

Deploy Server

Other Tools