Skip to main content
Glama
SEO-Review-Tools

SEO Review Tools - MCP server

Official

get_serp

Retrieve search engine results page data to analyze keyword performance and competitive rankings for SEO strategy development.

Instructions

Get SERP data from SEO Review Tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordYesThe keyword to search for.
hlYesThe language for the search results.
locationYesThe location for the search results.

Implementation Reference

  • The handler function `executeFunction` that fetches SERP data from the SEO Review Tools API using the provided keyword, language (hl), and location parameters.
    const executeFunction = async ({ keyword, hl, location }) => {
      const baseUrl = 'https://api.seoreviewtools.com';
      const apiKey = process.env.SEO_API_WORKSPACE_API_KEY;
      try {
        // Construct the URL with query parameters
        const url = new URL(`${baseUrl}/rankings/`);
        url.searchParams.append('keyword', keyword);
        url.searchParams.append('hl', hl);
        url.searchParams.append('location', location);
        url.searchParams.append('key', apiKey);
    
        // Perform the fetch request
        const response = await fetch(url.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 SERP data:', error);
        return { error: 'An error occurred while getting SERP data.' };
      }
    };
  • The input schema definition for the 'get_serp' tool, specifying parameters keyword, hl, and location as required strings.
        name: 'get_serp',
        description: 'Get SERP data from SEO Review Tools.',
        parameters: {
          type: 'object',
          properties: {
            keyword: {
              type: 'string',
              description: 'The keyword to search for.'
            },
            hl: {
              type: 'string',
              description: 'The language for the search results.'
            },
            location: {
              type: 'string',
              description: 'The location for the search results.'
            }
          },
          required: ['keyword', 'hl', 'location']
        }
      }
    }
  • lib/tools.js:7-16 (registration)
    Dynamic registration/discovery of all tools via `discoverTools()`, which imports `apiTool` from each file in `toolPaths`, including get-serp.js.
    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:1-10 (registration)
    Configuration listing paths to tool files, including 'seo-api-workspace/seo-ap-is-seo-review-tools/get-serp.js' at line 4, used for dynamic tool discovery.
    export const toolPaths = [
      'seo-api-workspace/seo-ap-is-seo-review-tools/get-website-traffic.js',
      'seo-api-workspace/seo-ap-is-seo-review-tools/get-authority.js',
      'seo-api-workspace/seo-ap-is-seo-review-tools/get-serp.js',
      'seo-api-workspace/seo-ap-is-seo-review-tools/post-bulk-website-traffic.js',
      'seo-api-workspace/seo-ap-is-seo-review-tools/get-backlinks.js',
      'seo-api-workspace/seo-ap-is-seo-review-tools/get-seo-content-score.js',
      'seo-api-workspace/seo-ap-is-seo-review-tools/get-keyword-statistics.js',
      'seo-api-workspace/seo-ap-is-seo-review-tools/get-keyword-suggestions.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 tool retrieves SERP data but fails to describe traits like whether it's read-only, requires authentication, has rate limits, or what the output format entails. This leaves significant gaps in understanding the tool's behavior.

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 with zero waste, front-loading the core purpose. It is appropriately sized for a simple tool, making it easy to parse without unnecessary details.

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 tool's complexity (3 parameters, no output schema, no annotations), the description is incomplete. It lacks details on behavioral traits, output format, and usage context, failing to compensate for the absence of structured data, which is inadequate for effective tool invocation.

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?

The input schema has 100% description coverage, clearly documenting the three required parameters (keyword, hl, location). The description adds no additional meaning beyond this, such as examples or constraints, so it meets the baseline score of 3 where the schema does the heavy lifting.

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 action ('Get SERP data') and the source ('from SEO Review Tools'), providing a specific verb and resource. However, it doesn't explicitly differentiate this tool from its siblings like 'get_keyword_statistics' or 'get_website_traffic', which might also involve search-related data, leaving some ambiguity about its unique scope.

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 offers no guidance on when to use this tool versus alternatives, such as its siblings. It lacks context on scenarios where SERP data is needed over other SEO metrics, prerequisites, or exclusions, leaving the agent without usage direction.

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