Skip to main content
Glama
SEO-Review-Tools

SEO Review Tools - MCP server

Official

get_keyword_suggestions

Generate keyword suggestions for SEO content planning using target keywords, language, and location parameters to improve search visibility.

Instructions

Get keyword suggestions from SEO Review Tools API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordYesThe keyword to get suggestions for.
hlNoThe language for the suggestions.
locationNoThe location for the suggestions.

Implementation Reference

  • The core handler function that fetches keyword suggestions from the SEO Review Tools API using the provided keyword, language (hl), and location parameters.
    const executeFunction = async ({ keyword, hl = 'English', location = 'United States' }) => {
      const baseUrl = 'https://api.seoreviewtools.com/v2/keyword-suggestions/';
      const apiKey = process.env.SEO_API_WORKSPACE_API_KEY;
      try {
        // Construct the URL with query parameters
        const url = new URL(baseUrl);
        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 keyword suggestions:', error);
        return { error: 'An error occurred while getting keyword suggestions.' };
      }
    };
  • The tool definition object including schema for input parameters, description, and reference to the handler function. This is the object exported and used for registration.
    const apiTool = {
      function: executeFunction,
      definition: {
        type: 'function',
        function: {
          name: 'get_keyword_suggestions',
          description: 'Get keyword suggestions from SEO Review Tools API.',
          parameters: {
            type: 'object',
            properties: {
              keyword: {
                type: 'string',
                description: 'The keyword to get suggestions for.'
              },
              hl: {
                type: 'string',
                description: 'The language for the suggestions.'
              },
              location: {
                type: 'string',
                description: 'The location for the suggestions.'
              }
            },
            required: ['keyword']
          }
        }
      }
    };
  • lib/tools.js:7-16 (registration)
    The discoverTools function dynamically imports the apiTool from each tool file (including get-keyword-suggestions.js) and collects them into an array for registration in the MCP system.
    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);
    }
  • List of all tool file paths used by discoverTools to load the get_keyword_suggestions tool among others.
    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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the API source but lacks details on rate limits, authentication needs, error handling, or the format of returned suggestions. For a tool with no annotations, this leaves significant gaps in understanding how it behaves operationally.

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 that directly states the tool's purpose without any unnecessary words. It is front-loaded and wastes no space, making it easy to parse quickly while conveying the essential information.

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 lack of annotations and output schema, the description is incomplete for effective tool use. It doesn't explain what the suggestions include (e.g., related keywords, volumes), how results are structured, or any behavioral traits like pagination. For a tool with three parameters and no structured output, more context is needed to guide an agent fully.

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 all three parameters. The description adds no additional meaning beyond what the schema provides, such as examples or usage tips. According to the rules, with high schema coverage, the baseline score is 3, as the schema adequately 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 action ('Get keyword suggestions') and the source ('from SEO Review Tools API'), which is specific and unambiguous. However, it doesn't explicitly differentiate this tool from sibling tools like 'get_keyword_statistics' or 'get_seo_content_score', which might also relate to keywords or SEO analysis, leaving some room for confusion about its unique role.

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. With sibling tools such as 'get_keyword_statistics' and 'get_seo_content_score' available, there is no indication of scenarios, prerequisites, or exclusions that would help an agent choose appropriately, relying solely on the tool name for inference.

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