Skip to main content
Glama

AgentSEO Domain Intersection

agentseo_domain_intersection
Destructive

Compare two domains to find shared keyword deficits, advantages, and target1-exclusive keyword opportunities.

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": {
      "target1": "<target1>",
      "target2": "<target2>"
    },
    "name": "agentseo_domain_intersection"
  }
}

Input Schema

NameRequiredDescriptionDefault
syncNo
limitNo
sort_byNoopportunity
target1Yes
target2Yes
languageNoen
locationNoUnited States
intersectionsNo
location_codeNo
min_search_volumeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior2/5

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

The description identifies the analytical findings but adds little operational behavior beyond the annotations. In particular, it does not explain why a comparison tool is annotated as destructive and non-idempotent, nor does it clarify external data retrieval, side effects, or synchronous versus asynchronous execution.

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?

The single sentence is compact and front-loaded, covering the comparison and its three intended findings without boilerplate. No wording is redundant, although additional operational detail would improve other dimensions.

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?

The basic goal is clear, but the definition is thin for a ten-parameter tool with no parameter descriptions or output schema. Domain input format, target roles beyond exclusivity, sync behavior, filtering and sorting semantics, and the destructive annotation all remain insufficiently explained.

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?

It clarifies that the two required targets are domains and gives target1 a meaningful orientation through 'target1-exclusive' opportunities. With 0% schema description coverage, however, it does not compensate for undocumented parameters such as sync, intersections, limit, sort_by, location_code, and min_search_volume.

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 gives a specific operation and resource: comparing two domains to identify shared keyword deficits, advantages, and target1-exclusive opportunities. The keyword and domain scope offers some implicit separation from page and backlink intersection siblings, but it does not explicitly distinguish this tool from related content-gap or keyword-analysis tools.

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?

Usage is implied for two-domain keyword gap analysis, with target1 identifying the perspective for exclusive opportunities. There is no explicit when-to-use or when-not-to-use guidance, prerequisite, or routing to alternatives such as agentseo_content_gap or agentseo_page_intersection.

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.