Skip to main content
Glama
Sign In

mowteng

by app.mowteng
OverviewDiscussionsAdmin

Find pages competing for a query

insights_cannibalization
Read-only

Google queries where two or more of the site's pages each take at least 10% of impressions, so they compete with each other.

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": {
      "siteUrl": "<siteUrl>"
    },
    "name": "insights_cannibalization"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoLength of each period in days (7-90), ending 3 days before today because Search Console data lags. Defaults to 28.
limitNoMaximum results (1-200). Defaults to 25.
siteUrlYesSearch Console property exactly as gsc_list_sites returns it: "https://example.com/" or "sc-domain:example.com"

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description contributes one genuinely useful behavioral fact — the 10%/2-page threshold that determines what qualifies as a result, which explains empty results. It says nothing about the returned shape, whether quantities are impression-weighted, or which date window the comparison uses.

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?

A single sentence with zero filler, and the decisive information (the competition threshold) is front-loaded. Nothing in it is redundant or could be trimmed without losing meaning.

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 annotations and a fully documented schema, the input side is complete. However, no output schema exists, and the description never indicates what a result contains (query, competing page URLs, impression shares), leaving an agent unable to anticipate the response.

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

Parameters3/5

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

Schema description coverage is 100%, with days, limit and siteUrl all documented in the schema including ranges and the 3-day lag rationale. The description adds no parameter-level meaning beyond that, so the baseline of 3 applies.

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 names a concrete resource (Google queries) and gives a precise detection rule: two or more of the site's pages each capturing at least 10% of impressions. That makes it distinguishable from analytics-style siblings such as gsc_search_analytics, though it never explicitly contrasts itself with the other insights_* tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use statement, no prerequisite (e.g. 'requires a verified Search Console property', which the siteUrl parameter implies), and no mention of alternatives like insights_striking_distance. Usage is only inferable from the tool name and the criterion described.

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

All mowteng toolsInspect
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