Murkuz SEO

Opportunity_Matrix

Rank pages by where effort actually pays off, by crossing search ranking potential against GA4 conversion rate. When at least one candidate page has a measured GA4 conversion, every page lands in one of four groups: rank_up_now (close to page one already and converts well, push it), improve_page_first (real ranking potential but converts poorly, fix the page before chasing more traffic to it), protect (already converts well but limited further ranking room, do not break what works), deprioritise (neither), returned under quadrants with quadrants_assigned: true. The split point on each axis is that axis's own median across the pages being compared, and both medians are returned so the split is auditable rather than a hidden cutoff. When NO candidate page has a measured GA4 conversion in this window, which is the normal case for a site without conversion tracking enabled, the conversion axis carries no signal: a median of zero would put every page 'at or above median' and mislabel all of them, protect included, so quadrants are not assigned. The response instead carries quadrants_assigned: false and a ranked_by_potential_only list, pages ranked by search ranking potential alone, with a note explaining why. Only pages with both a Search Console ranking signal and a measured GA4 session count are placed; a page missing one side cannot be scored honestly and is left out rather than scored with a zero. Both limit and offset apply per quadrant, and the pagination block carries one entry per quadrant, so a quadrant holding 80 pages is never mistaken for one holding 20. PAGING: this returns one page of rows. The pagination block reports returned, total_available, truncated and next_offset for every list in the response. Check truncated before drawing a conclusion: when it is true these rows are a slice, not the whole picture, and a total or a 'none of them' claim built on them is wrong. Read the rest with offset set to next_offset, or raise limit.

Input Schema

Name	Required	Description
`days`	No	Window length in days. Default 28.
`limit`	No	Max pages returned per quadrant. Default 20.
`offset`	No	Row offset into the full result set. Default 0. To read the next page, pass the value the response reports under pagination.<list>.next_offset.
`site_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.6/5.0

Behavior5/5

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

With no annotations to lean on, the description carries the full burden and does so: it discloses the median split points and that both medians are returned, explains why quadrants are skipped when the conversion axis has no signal (a zero median would mislabel every page including 'protect'), and states the exclusion rule for pages missing either data side.

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-loaded with the core purpose and the payoff framing, then behavior, then paging. It is long, and the PAGING paragraph partially restates the truncation point, but nearly every sentence adds a constraint an agent would otherwise get wrong.

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?

With no output schema, the description must describe the return shape, and it does: quadrants_assigned boolean, the ranked_by_potential_only fallback list with an explanatory note, and the per-list pagination block reporting returned/total_available/truncated/next_offset. An agent has everything needed to call and interpret 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 coverage is 75%, and the description adds real meaning beyond it: limit and offset apply per quadrant, so a quadrant of 80 is not mistaken for 20, and offset should be fed the response's next_offset. It doesn't clarify the days window semantics, which the schema already covers reasonably.

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 ('rank pages') plus the exact resource and the two axes being crossed (Search Console ranking potential vs GA4 conversion rate). The four quadrant names make it immediately distinguishable from siblings like Landing_Page_Diagnosis or Live_Quick_Wins.

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?

Clearly delineates the two operating regimes: when at least one page has a measured GA4 conversion versus when none do, and what changes in the response in each case. It does not name a sibling alternative to use instead, so it falls short of the explicit when/when-not/alternatives bar.

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

All Murkuz SEO 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?