Skip to main content
Glama
SEO-Review-Tools

SEO Review Tools - MCP server

Official

post_bulk_website_traffic

Submit multiple domain names to retrieve traffic estimates and location-based data for SEO analysis.

Instructions

Post bulk website traffic data to SEO Review Tools API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainsYesAn array of domain names to check traffic for.
locationNoThe location for the traffic data.
hlNoThe language for the traffic data.

Implementation Reference

  • The core handler function `executeFunction` that performs the POST request to the SEO Review Tools API bulk website traffic endpoint, handling domains array, location, and language parameters, and returns the API response or error.
    const executeFunction = async ({ domains, location = 'United States', hl = 'English' }) => {
      const baseUrl = 'https://api.seoreviewtools.com/v2/bulk-website-traffic/';
      const token = process.env.SEO_API_WORKSPACE_API_KEY;
      try {
        // Prepare the request body
        const body = JSON.stringify({ domains });
    
        // Set up the URL with query parameters
        const url = new URL(baseUrl);
        url.searchParams.append('key', token);
        url.searchParams.append('location', location);
        url.searchParams.append('hl', hl);
    
        // Perform the fetch request
        const response = await fetch(url.toString(), {
          method: 'POST',
          headers: {
            'Content-Type': 'application/json',
            'X-API-Key': token
          },
          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 posting bulk website traffic data:', error);
        return { error: 'An error occurred while posting bulk website traffic data.' };
      }
    };
  • The JSON schema definition for the tool, including name 'post_bulk_website_traffic', description, input parameters (domains required array of strings, optional location and hl strings).
      type: 'function',
      function: {
        name: 'post_bulk_website_traffic',
        description: 'Post bulk website traffic data to SEO Review Tools API.',
        parameters: {
          type: 'object',
          properties: {
            domains: {
              type: 'array',
              items: {
                type: 'string',
                description: 'An array of domain names to check traffic for.'
              },
              description: 'An array of domain names to check traffic for.'
            },
            location: {
              type: 'string',
              description: 'The location for the traffic data.'
            },
            hl: {
              type: 'string',
              description: 'The language for the traffic data.'
            }
          },
          required: ['domains']
        }
      }
    }
  • tools/paths.js:5-5 (registration)
    The tool file path is registered in the toolPaths array, which is used by lib/tools.js to dynamically import and register the tool.
    'seo-api-workspace/seo-ap-is-seo-review-tools/post-bulk-website-traffic.js',
  • lib/tools.js:7-16 (registration)
    The `discoverTools` function dynamically imports each tool file from toolPaths and extracts the `apiTool` object for registration, making 'post_bulk_website_traffic' available.
    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);
    }
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 posts data to an API but doesn't clarify whether this is a write operation, what permissions or authentication might be required, potential side effects (e.g., data overwriting), rate limits, or error handling. This leaves significant gaps for a tool that likely mutates data.

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 function without unnecessary words. It is appropriately sized and front-loaded, 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 lack of annotations and output schema, the description is incomplete for a tool that likely performs a write operation. It doesn't address behavioral aspects like authentication needs, data persistence, or response format, which are critical for an agent to use the tool correctly and safely.

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 schema fully documents the three parameters (domains, location, hl). The description adds no additional meaning beyond what the schema provides, such as explaining the relationship between parameters or usage nuances. This meets the baseline for high schema coverage.

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 ('Post bulk website traffic data') and target ('SEO Review Tools API'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_website_traffic', which appears to retrieve rather than submit data, leaving some ambiguity about when to use each.

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, such as the sibling 'get_website_traffic'. It lacks context about prerequisites, use cases, or exclusions, leaving the agent to infer usage based on the tool 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