Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

get_page_detail

Retrieve daily clicks, impressions, CTR, and position for a single page URL in a Search Console property, using the same date-range syntax as summary reports.

Instructions

Daily time series (clicks, impressions, CTR, position) for a single page URL in a property. Drop-in compatible with the summary's date-range syntax.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_page_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the returned metrics and daily granularity, which is useful, but it does not explain date-range defaults, URL handling, or output behavior beyond the metric list.

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 definition is two compact sentences and front-loads the returned metrics. The phrase 'Drop-in compatible with the summary's date-range syntax' is efficient but somewhat opaque without knowing the summary tool.

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?

For a tool with no output schema, the description does well to list the returned metrics. However, it leaves important operational details unclear, especially how a page URL and date range are specified when the input schema is an empty object.

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?

The schema exposes zero parameters, so the baseline is 4. The description adds semantic context by referencing a single page URL and date-range compatibility, though it does not explain how those values are supplied given the empty schema.

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 clearly specifies the resource and scope: daily time series of clicks, impressions, CTR, and position for a single page URL in a property. It implicitly distinguishes from multi-page or summary tools, but does not explicitly name an alternative.

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?

Usage is implied by 'single page URL in a property' and the reference to the summary's date-range syntax. However, there is no explicit guidance on when to use this versus related tools such as get_top_pages, page_explorer, or get_gsc_summary.

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