Skip to main content
Glama

AgentSEO Backlinks List

agentseo_backlinks_list

Return a bounded list of actionable backlinks and classify each one for protection, repair, reclaim, quality review, or outreach reference.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoone_per_domain
syncNo
limitNo
offsetNo
targetYes
sort_byNorank
min_rankNo
rank_scaleNoone_hundred
broken_onlyNo
dofollow_onlyNo
intersection_modeNopartial
include_subdomainsNo
backlinks_status_typeNolive
include_indirect_linksNo
exclude_internal_backlinksNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, description carries full burden but only states return of classified list. Omits critical behavioral traits such as pagination (limit/offset), filtering, read-only nature, or any side effects.

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?

Extremely concise but under-specified. The one-sentence description is front-loaded but fails to convey necessary detail for a tool with many parameters.

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?

Given 15 parameters, no output schema, no annotations, and many sibling tools, the description is severely incomplete. Does not explain output format, classification criteria, or how to leverage parameters effectively.

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%. Description does not explain any of the 15 parameters (e.g., target, mode, intersection_mode). Users must infer meaning solely from schema property names and enums.

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?

Clearly states the tool returns a bounded list of actionable backlinks and classifies them, with specific categories. Distinguishes from sibling backlinks tools by focusing on actionability and classification.

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?

No guidance on when to use this tool vs. alternatives like agentseo_backlinks_summary, agentseo_backlinks_opportunity_finder, or others. Lacks any context for selection.

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.