Skip to main content
Glama
Sign In
AgentSEO MCP Server

AgentSEO MCP Server

by AgentSEO-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

AgentSEO Backlinks New/Lost Timeseries

agentseo_backlinks_new_lost_timeseries
Destructive

Track new and lost backlinks and referring domains over time, aggregate them by day, week, month, or year, and classify link momentum, leakage, and volatility.

Instructions

Track new and lost backlinks/referring domains over time and classify link momentum, leakage, and volatility. Uses AgentSEO credits; repeating the call can create new charged work.

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_backlinks_new_lost_timeseries"
  }
}

Input Schema

NameRequiredDescriptionDefault
syncNoRequest a bounded wait for completion when true. The API can still return a pending job; retain its job ID and poll agentseo_job_status instead of repeating this charged call. False returns a queued job without waiting. Type: Boolean. Default: true.
targetYesTarget domain, subdomain or absolute page URL to analyze; use a hostname or URL, not a business name. Type: String. Minimum: 1 characters. Required.
date_toNoEnd of the requested reporting date range in YYYY-MM-DD format; must not precede date_from. Type: String. Format must match /^\d{4}-\d{2}-\d{2}$/. Optional; no client default.
date_fromNoBeginning of the requested reporting date range in YYYY-MM-DD format. Type: String. Format must match /^\d{4}-\d{2}-\d{2}$/. Optional; no client default.
group_rangeNoCalendar interval used to aggregate the new/lost backlink time series. Type: String. Accepted values: "day", "week", "month", "year". Default: "month".month
include_subdomainsNoInclude links or ranking data for subdomains of the target when true. Type: Boolean. Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.5
    • addedInput schema / properties / date_from / description
      Added value: +"Beginning of the requested reporting date range in YYYY-MM-DD format. Type: String. Format must match /^\\d{4}-\\d{2}-\\d{2}$/. Optional; no client default."
    • addedInput schema / properties / date_to / description
      Added value: +"End of the requested reporting date range in YYYY-MM-DD format; must not precede date_from. Type: String. Format must match /^\\d{4}-\\d{2}-\\d{2}$/. Optional; no client default."
    • addedInput schema / properties / group_range / description
      Added value: +"Calendar interval used to aggregate the new/lost backlink time series. Type: String. Accepted values: \"day\", \"week\", \"month\", \"year\". Default: \"month\"."
    • addedInput schema / properties / include_subdomains / description
      Added value: +"Include links or ranking data for subdomains of the target when true. Type: Boolean. Default: true."
    • addedInput schema / properties / sync / description
      Added value: +"Request a bounded wait for completion when true. The API can still return a pending job; retain its job ID and poll agentseo_job_status instead of repeating this charged call. False returns a queued job without waiting. Type: Boolean. Default: true."
    • addedInput schema / properties / target / description
      Added value: +"Target domain, subdomain or absolute page URL to analyze; use a hostname or URL, not a business name. Type: String. Minimum: 1 characters. Required."
  2. First observedv0.1.4

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety bar is lower. The description adds genuinely new operational context: the call consumes AgentSEO credits and repeating it can spawn additional charged work, reinforcing the non-idempotent annotation with a concrete cost consequence.

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?

Two sentences, front-loaded with the capability and followed by the cost warning. No filler, no repetition of schema or annotation content, and the most decision-relevant caveat is placed where it will be read.

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

Completeness4/5

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

With no output schema, the description does name the analytical outputs (momentum, leakage, volatility) that the caller should expect. The sync/pending-job handling and date-range constraints are fully covered by the schema, leaving only minor gaps around result shape for a six-parameter tool.

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%, so all six parameters including date_from/date_to, group_range and sync are already documented with formats and defaults. The description adds no parameter-level meaning beyond the generic 'over time' framing, so the baseline 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?

States a specific verb and resource: tracking new and lost backlinks/referring domains over time, plus derived metrics (momentum, leakage, volatility). The 'over time' timeseries framing distinguishes it from sibling backlink tools such as backlinks_summary, backlinks_list, and backlinks_referring_domains, though no sibling is named explicitly.

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?

The credit warning implies this is a paid, non-repeatable call, which nudges the agent toward polling agentseo_job_status rather than re-invoking. However, it never states when to pick this timeseries tool over the other backlink siblings, nor what preconditions (e.g., a prior summary) apply.

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