Skip to main content
Glama
Teake1404

seo-data-api-mcp-server

by Teake1404

Backlinks Summary

backlinksSummary

Retrieve extended backlink statistics for any domain, host, or URL. Compare your profile against competitors with automated analysis prompts for specific keywords.

Instructions

Fetch extended backlink statistics for one or multiple targets. Optionally builds an analysis prompt comparing your domain vs a competitor for a given keyword (v1/backlinks/summary)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesSingle target or an array of targets (root domain, host, or full URL). When omitted, it defaults to [domain, competitor] if both are provided.
modeNoScope of analysis: 'domain' (*.example.com/* incl. subdomains), 'host' (www.example.com/* only), or 'url' (single URL). Default: host.host
outputNoResponse format. Default: json.json
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits like whether the tool is read-only, what 'extended' statistics entail, rate limits, or auth requirements. The term 'optionally builds an analysis prompt' is vague.

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 two sentences, front-loaded with the core action, but the mention of an optional analysis prompt introduces some ambiguity without adding structure.

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 no output schema, no annotations, and many sibling tools, the description lacks sufficient context about how the summary relates to other backlinks tools, what output to expect, and how to use the optional prompt feature.

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 coverage is 100% with parameter descriptions, so baseline 3. The description adds only marginal meaning about an optional analysis prompt not reflected in the schema, but does not clarify parameter semantics further.

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 fetches extended backlink statistics for one or multiple targets, and mentions an optional analysis prompt for competitor comparison, which distinguishes it from sibling tools focusing on specific backlink data like anchors or refdomains.

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 description hints at a competitor comparison use case but provides no explicit when-to-use or when-not-to-use guidance, nor direct alternatives among the many backlink sibling tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Teake1404/seo-data-api-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server