Skip to main content
Glama
SEO-Review-Tools

SEO Review Tools - MCP server

Official

get_backlinks

Retrieve backlink data for any URL to analyze referring domains and inbound links for SEO assessment.

Instructions

Get backlinks for a specified URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL for which to retrieve backlinks.
unique_domainsNoWhether to return unique domains (1 for yes, 0 for no).

Implementation Reference

  • The executeFunction implements the core logic for fetching backlinks from the SEO Review Tools API using the provided URL and optional unique_domains parameter.
    const executeFunction = async ({ url, unique_domains = 1 }) => {
      const baseUrl = 'https://api.seoreviewtools.com/backlinks/';
      const apiKey = process.env.SEO_API_WORKSPACE_API_KEY;
      try {
        // Construct the URL with query parameters
        const urlWithParams = new URL(baseUrl);
        urlWithParams.searchParams.append('url', url);
        urlWithParams.searchParams.append('unique_domains', unique_domains.toString());
        urlWithParams.searchParams.append('key', apiKey);
    
        // Perform the fetch request
        const response = await fetch(urlWithParams.toString(), {
          method: 'GET',
          headers: {
            'Content-Type': 'application/json'
          }
        });
    
        // Check if the response was successful
        if (!response.ok) {
          const errorData = await response.json();
          throw new Error(errorData);
        }
    
        // Parse and return the response data
        const data = await response.json();
        return data;
      } catch (error) {
        console.error('Error getting backlinks:', error);
        return { error: 'An error occurred while getting backlinks.' };
      }
    };
  • The tool schema defining the name, description, parameters (url required, unique_domains optional), used for MCP tool registration.
      name: 'get_backlinks',
      description: 'Get backlinks for a specified URL.',
      parameters: {
        type: 'object',
        properties: {
          url: {
            type: 'string',
            description: 'The URL for which to retrieve backlinks.'
          },
          unique_domains: {
            type: 'integer',
            description: 'Whether to return unique domains (1 for yes, 0 for no).'
          }
        },
        required: ['url']
      }
    }
  • tools/paths.js:6-6 (registration)
    The path to the get_backlinks tool implementation file is listed in toolPaths for dynamic discovery.
    'seo-api-workspace/seo-ap-is-seo-review-tools/get-backlinks.js',
  • lib/tools.js:8-14 (registration)
    The discoverTools function dynamically imports each tool file (including get-backlinks.js) and extracts the apiTool object containing handler and schema for MCP server registration.
    const toolPromises = toolPaths.map(async (file) => {
      const module = await import(`../tools/${file}`);
      return {
        ...module.apiTool,
        path: file,
      };
    });
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states what the tool does but lacks details on traits like rate limits, authentication needs, response format, or potential errors. For a data retrieval tool with no annotation coverage, this is a significant gap in transparency.

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?

The description is a single, efficient sentence: 'Get backlinks for a specified URL.' It is front-loaded with the core purpose, has zero waste, and is appropriately sized for a simple tool. Every word earns its place by conveying essential information without redundancy.

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

Completeness3/5

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

Given the tool's low complexity (2 parameters, no output schema, no annotations), the description is minimally adequate. It states the purpose but lacks context on usage, behavioral traits, or output details. Without annotations or an output schema, the description should do more to compensate, but it only meets the bare minimum for a read-only data 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%, meaning the input schema fully documents both parameters ('url' and 'unique_domains'). The description adds no additional meaning beyond what the schema provides, such as explaining the significance of backlinks or how 'unique_domains' affects results. Baseline 3 is appropriate when the schema handles parameter documentation.

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 the tool's purpose: 'Get backlinks for a specified URL.' It specifies the verb ('Get') and resource ('backlinks'), and the scope ('for a specified URL') is unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_authority_scores' or 'get_serp', which might also relate to SEO data but serve different purposes.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools or contexts where this tool is preferred, such as for SEO analysis versus other metrics. Without any usage context or exclusions, the agent must infer when this tool is appropriate based on the name alone.

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/SEO-Review-Tools/SEO-API-MCP'

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