Skip to main content
Glama
SEO-Review-Tools

SEO Review Tools - MCP server

Official

get_authority_scores

Calculate domain and page authority scores for multiple URLs to assess SEO performance and identify improvement opportunities.

Instructions

Get authority scores for a list of URLs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlsYesThe list of URLs to check authority scores for.
metricsNoThe metrics to retrieve, default is "pa|da".

Implementation Reference

  • The main handler function `executeFunction` that fetches authority scores (PA/DA metrics) for a list of URLs using the SEO Review Tools API.
    const executeFunction = async ({ urls, metrics = 'pa|da' }) => {
      const baseUrl = 'https://api.seoreviewtools.com/bulk-authority-score/';
      const token = process.env.SEO_API_WORKSPACE_API_KEY;
    
      try {
        // Prepare the request body
        const body = JSON.stringify({ urls });
    
        // Set up headers for the request
        const headers = {
          'Content-Type': 'application/json',
          'X-API-Key': token
        };
    
        // Perform the fetch request
        const response = await fetch(`${baseUrl}?metrics=${metrics}&key=${token}`, {
          method: 'POST',
          headers,
          body
        });
    
        // 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 authority scores:', error);
        return { error: 'An error occurred while getting authority scores.' };
      }
    };
  • The JSON schema defining the input parameters for the tool: `urls` (required array of strings) and optional `metrics` (string).
    parameters: {
      type: 'object',
      properties: {
        urls: {
          type: 'array',
          items: {
            type: 'string'
          },
          description: 'The list of URLs to check authority scores for.'
        },
        metrics: {
          type: 'string',
          description: 'The metrics to retrieve, default is "pa|da".'
        }
      },
      required: ['urls']
    }
  • lib/tools.js:7-16 (registration)
    Dynamic registration of the tool via `discoverTools()` which imports the `apiTool` export from get-authority.js (via paths.js) and includes it in the list of available MCP tools.
    export async function discoverTools() {
      const toolPromises = toolPaths.map(async (file) => {
        const module = await import(`../tools/${file}`);
        return {
          ...module.apiTool,
          path: file,
        };
      });
      return Promise.all(toolPromises);
    }
  • tools/paths.js:3-3 (registration)
    The tool path is listed in `toolPaths` array, used by discoverTools to load the specific tool file.
    'seo-api-workspace/seo-ap-is-seo-review-tools/get-authority.js',
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action but lacks details on permissions, rate limits, response format, or error handling. For a tool that likely involves external API calls or data retrieval, this omission is significant, though it doesn't contradict any annotations.

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, direct sentence with no wasted words, front-loading the core action and resource. It efficiently communicates the essential purpose without unnecessary elaboration, making it easy to parse quickly.

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 complexity of SEO tools and the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'authority scores' are, how results are returned, or any behavioral traits, leaving gaps that could hinder effective tool selection and invocation by an AI agent.

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 the input schema already documents both parameters ('urls' and 'metrics') clearly. The description adds no additional meaning beyond what's in the schema, such as explaining what 'authority scores' entail or how metrics like 'pa|da' are interpreted, meeting the baseline for adequate but not enhanced parameter context.

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 verb ('Get') and resource ('authority scores for a list of URLs'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'get_website_traffic' or 'get_seo_content_score', which might also involve URL analysis but for different metrics, leaving some ambiguity about its specific niche.

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 like 'get_website_traffic' or 'get_seo_content_score', nor does it specify prerequisites, contexts, or exclusions, leaving the agent to infer usage based on tool names 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