Mark

Get Page Detail

get_page_detail

Read-onlyIdempotent

Reports everything Mark knows about one page URL for a date range: Search Console clicks, impressions, CTR, position and top queries for that page; tracked keywords whose latest rank is that page; its issues in the latest site audit; Mark posts published at it or linking to it; first-touch leads that landed on it, with conversion rate and the Top pages Leak or Write more signal; site tag leads (lead_submitted events in the workspace's PostHog project whose visit started on it, shown beside leads and never added to them; siteTagLeads.state is ready, no-posthog, no-signal or failed, with reason: busy means PostHog didn't answer in time (it runs 3 queries at once per project and queues the rest), so try again in a minute; the PostHog connection is fine. error is any other failure, such as lost access, so check the PostHog connection.); and buyer questions whose AI answers cited it. Each block says why when it has no data. Pass the page URL exactly as get_search_performance returns it, scheme included, or Search Console may find no rows for it. The URL must be on this workspace's Search Console property, or on one of its sites with none. Does not change anything. Related: get_search_performance, get_site_audit, get_rankings, get_ai_visibility.

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

Input Schema

Name	Required	Description
`to`	No	Range end YYYY-MM-DD.
`url`	Yes	The page URL, as get_search_performance returns it.
`from`	No	Range start YYYY-MM-DD. Defaults to the last 28 settled days.
`marketId`	No	Filter Search Console to one active market's country, as the page view's market picker does.
`compareTo`	No	Prior period end YYYY-MM-DD. Requires compareFrom.
`compareFrom`	No	Prior period start YYYY-MM-DD. Requires compareTo.

Output Schema

Name	Required	Description	Default
`url`	Yes
`appUrl`	Yes
`blocks`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 14, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), but the description adds substantial behavioral context: every empty block explains why it has no data, siteTagLeads.state enumerates the four states, 'busy' vs 'error' reasons are explained with retry guidance, and the PostHog connection caveat is spelled out.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The resource and key requirement are front-loaded, and nearly every clause carries information. But the bulk sits inside one enormous sentence with deeply nested parentheses (the siteTagLeads aside), which makes it hard to scan and parse.

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?

For a six-parameter read-only aggregation tool with an output schema and full annotation coverage, the description supplies everything an agent needs: what is aggregated, URL form requirements, scope constraints, and failure-mode semantics. Return-value detail is optional given the output schema, so the extra block listing is a bonus rather than a gap.

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 coverage is 100%, so the baseline is 3, but the description adds genuine meaning: the URL must be the exact canonical form returned by get_search_performance and must belong to the workspace's GSC property or one of its sites. It doesn't add anything for marketId or the compareFrom/compareTo pairing beyond 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?

The opening states a specific verb and resource — 'Reports everything Mark knows about one page URL' — and then enumerates the exact blocks returned (Search Console metrics, ranked keywords, site-audit issues, posts, first-touch leads, site-tag leads, buyer questions). It explicitly distinguishes itself from siblings by listing the related tools (get_search_performance, get_site_audit, get_rankings, get_ai_visibility) whose data it aggregates.

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 concrete preconditions: pass the URL exactly as get_search_performance returns it, scheme included, and it must be on the workspace's Search Console property. However, it lists related tools without stating when to prefer them over this one (e.g., when you only need rankings, use get_rankings).

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

All Mark tools Inspect

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

Need Help?