Skip to main content
Glama
Sign In
SE Ranking MCP Server

SE Ranking MCP Server

by TeamDay-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List New and Lost Referring Domains

DATA_listNewLostReferringDomains

Identify newly found and lost referring domains for a target within a specified date range. Use this data to monitor backlink profile changes.

Instructions

Data Tool: Returns a list of referring domains, at least one backlink from which was (newly) found or lost in the specified date range for the specified target.

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": "DATA_listNewLostReferringDomains"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNohost
limitNo
targetYesAim of the request: root domain, host, or URL.
date_toNoEnd date in YYYY-MM-DD format.
order_byNonew_lost_date
date_fromNoStart date in YYYY-MM-DD format.
new_lost_typeNoIndicates whether the refdomain is new or lost. Empty returns both.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations provided, so description must carry behavioral disclosure. It only states the basic function, missing details on pagination, sorting, limit behavior, or whether new_lost_type filters. The description does not add significant behavioral context beyond the schema.

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?

The description is a single sentence that front-loads 'Data Tool:' and states the core function concisely. It is efficient but could be structured with separate usage hints for better clarity.

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?

Given 7 parameters, no output schema, and no annotations, the description is incomplete. It lacks details on ordering, filtering, limit behavior, and return format, which are important for an agent to use the tool correctly.

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 57% (4/7 parameters have descriptions), but the tool description does not elaborate on any parameter meanings beyond what the schema provides. For example, it doesn't explain mode or order_by options. The description adds minimal semantic value.

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?

The description clearly states the tool returns a list of referring domains with a specific condition (newly found or lost) in a date range. It distinguishes from siblings like DATA_getNewLostRefDomainsCount and DATA_listNewLostBacklinks by specifying 'list' and 'referring domains'.

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?

No explicit guidance on when to use this tool versus alternatives like count or backlinks tools. Usage is implied by the description of returning a list, but no when-not or alternative mentioned.

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

Deploy Server

Other Tools