Skip to main content
Glama
TeamDay-AI

SE Ranking MCP Server

by TeamDay-AI

Backlinks Summary

DATA_getBacklinksSummary

Retrieve a summary of backlink metrics for one or multiple targets, including domains, subdomains, or URLs.

Instructions

Data Tool: Retrieves a summary of backlink metrics for one or multiple targets (domains, subdomains, or URLs).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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
targetYesSingle target or an array of targets (root domain, host, or full URL). When omitted, it defaults to [domain, competitor] if both are provided.
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'retrieves a summary' without specifying what metrics are included, whether it is read-only, or any other behavioral details.

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, clear sentence that is front-loaded with the tool category and purpose. It is concise but could include more context.

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 the large number of sibling backlink tools and the lack of output schema, the description is incomplete. It does not specify what the summary contains or how it differs from similar tools.

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 descriptions for all parameters. The description adds no additional meaning beyond the schema, so baseline of 3 is appropriate.

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 clearly states it retrieves a summary of backlink metrics for targets, but does not differentiate from sibling tools like DATA_getBacklinksMetrics or DATA_getBacklinksCount.

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 versus other backlink tools. The description does not provide context for appropriate usage or exclusions.

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/TeamDay-AI/se-ranking-mcp'

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