Skip to main content
Glama

AgentSEO Backlinks Page Intersection

agentseo_backlinks_page_intersection
Destructive

Find source pages that link to competitor targets but not excluded/user targets, then prioritize link-gap outreach and quality review.

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": {
      "targets": "<targets>"
    },
    "name": "agentseo_backlinks_page_intersection"
  }
}

Input Schema

NameRequiredDescriptionDefault
syncNo
limitNo
offsetNo
sort_byNorank
targetsYes
min_rankNo
rank_scaleNoone_hundred
broken_onlyNo
dofollow_onlyNo
min_page_rankNo
max_spam_scoreNo
exclude_targetsNo
min_domain_rankNo
include_subdomainsNo
internal_list_limitNo
backlinks_status_typeNolive
include_indirect_linksNo
exclude_internal_backlinksNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations declare destructiveHint=true, readOnlyHint=false, and non-idempotent, yet the description frames this purely as a finder/analysis step with no warning about side effects, cost, or mutation. It also says nothing about pagination limits (limit max 100, offset max 20000), the sync/async flag, or rate/credit implications for an openWorld tool. With annotations this permissive, the description should either confirm or explain the destructive behavior and does neither.

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?

A single front-loaded sentence with the intersection rule first and the downstream purpose second; no filler or repetition. It is efficiently written, arguably too terse for an 18-parameter tool, but nothing is wasted.

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

Completeness2/5

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

For a tool with 18 parameters, no output schema, and no schema descriptions, one sentence is insufficient: filtering semantics, default behavior (sync=true), result shape, and the meaning of the destructive/ non-idempotent annotations are all unaddressed. An agent could call it, but only by guessing at most parameters.

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

Parameters2/5

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

Schema description coverage is 0% across 18 parameters, so the description carries the full burden, and it only clarifies two of them: targets means competitor domains/pages and exclude_targets means the user's own targets. Nothing is said about rank_scale, min_rank vs min_page_rank vs min_domain_rank, max_spam_score, backlinks_status_type, include_indirect_links, internal_list_limit, or include_subdomains, leaving most of the tuning surface undocumented.

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 uses a specific verb and resource ('Find source pages that link to...') and states the intersection logic (targets minus excluded), which separates it from agentseo_backlinks_list and agentseo_domain_intersection (domains, not pages). It is clear about what is returned at a high level, though it never names the sibling it replaces, so the differentiation is inferred rather than stated.

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?

'Prioritize link-gap outreach and quality review' implies the link-gap use case but gives no explicit when-to-use or when-not-to-use guidance relative to backlinks_opportunity_finder, backlinks_competitors, or page_intersection. An agent must infer which backlink tool is appropriate from the intersection framing alone.

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.