Skip to main content
Glama

AgentSEO Domain Relevant Pages

agentseo_domain_relevant_pages
Destructive

Find traffic-carrying pages for a domain and route them into protect, refresh, expand, or recover actions.

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": {
      "target": "<target>"
    },
    "name": "agentseo_domain_relevant_pages"
  }
}

Input Schema

NameRequiredDescriptionDefault
syncNo
limitNo
targetYes
sort_byNoestimated_traffic
languageNoen
locationNoUnited States
min_trafficNo
location_codeNo
historical_serp_modeNolive

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations declare destructiveHint=true, readOnlyHint=false, idempotentHint=false, and openWorldHint=true, so the description's 'route them into protect, refresh, expand, or recover actions' is at least directionally consistent — but it never says WHAT gets mutated or destroyed, whether routing is a write to stored state or just a returned recommendation, or whether it is reversible. With a destructive write annotation, the description should disclose the side effects, cost, or approval requirements but says nothing. The 'sync' parameter's behavior also goes unexplained.

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?

It is a single tight sentence with no filler, which is good. However, the second half is vague jargon ('route them into protect, refresh, expand, or recover actions') that consumes the remaining space without conveying actionable information. Efficient in length but not in information density.

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

Completeness1/5

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

A tool with nine parameters, zero schema description coverage, a destructive write annotation, and no output schema demands substantial description; this one provides a single ambiguous sentence. An agent has no way to know what the tool returns, what side effects occur, or how to configure any parameter. This is grossly incomplete for the tool's complexity.

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

Parameters1/5

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

Schema description coverage is 0% across nine parameters, so the description carries the full burden of explaining them — and it explains none. Critical semantics like 'sync', 'historical_serp_mode' (live/lost/all), the interaction between 'location' and 'location_code', 'min_traffic', and 'sort_by' are entirely undocumented anywhere. An agent cannot infer safe values for these from the description.

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 specific verb and resource: find traffic-carrying pages for a domain. That distinguishes it reasonably from siblings like agentseo_domain_ranked_keywords or agentseo_backlinks_domain_pages, though it never names those alternatives explicitly. The trailing clause about routing into protect/refresh/expand/recover actions muddies rather than sharpens the stated purpose.

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 explicit when-to-use guidance, no prerequisites, and no mention of when a different sibling tool would be the better choice. The implied use case (auditing a domain's traffic-generating pages) is inferable but never stated as a condition. An agent is left to guess the relationship between this tool and the many overlapping domain/content tools in the list.

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.