Skip to main content
Glama

MetricPort

Queries for one page

gsc_page_queries
Read-onlyIdempotent

All queries a single URL ranks for, with clicks, impressions, CTR and position. Use to understand what a page is known for and which secondary keywords to strengthen.

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": {
      "property": "<property>",
      "url": "<url>"
    },
    "name": "gsc_page_queries"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFull URL or a path substring
daysNo
limitNo
propertyYesSearch Console property id from list_properties, e.g. sc-domain:example.com or https://www.example.com/

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower. The description adds the return metrics, which is useful given no output schema, but says nothing about the time window actually queried, row capping, or ordering.

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 tight sentences, zero filler. The return content is front-loaded and the use case follows, each earning its place.

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

Completeness3/5

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

With no output schema, listing the returned metrics is necessary and present. However, for a time-windowed analytics read, the absence of any statement about the default 90-day range and the 200-row cap leaves gaps an agent would need to infer from the schema defaults.

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?

Schema description coverage is only 50%: 'days' and 'limit' have defaults and bounds but no description, and the description supplies no parameter guidance at all. Saying 'All queries' is faintly at odds with a default limit of 200, and the 90-day default window is never surfaced.

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?

Specific verb+resource: 'All queries a single URL ranks for, with clicks, impressions, CTR and position' tells the agent exactly what is returned and the scope ('a single URL'). That scope implicitly separates it from gsc_top_queries and gsc_top_pages, though no sibling is named explicitly.

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?

Gives a clear use case: understanding what a page is known for and which secondary keywords to strengthen. It stops short of naming alternatives (e.g. gsc_top_queries for site-wide queries) or stating when this is the wrong choice.

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.