Skip to main content
Glama
SEO-Review-Tools

SEO Review Tools - MCP server

Official

get_website_traffic

Retrieve website traffic estimates and analytics data for any URL to analyze visitor volume and engagement metrics.

Instructions

Get website traffic data from SEO Review Tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL of the website to get traffic data for.

Implementation Reference

  • The main handler function that fetches website traffic data from the SEO Review Tools API endpoint.
    const executeFunction = async ({ url }) => {
      const baseUrl = 'https://api.seoreviewtools.com';
      const apiKey = process.env.SEO_API_WORKSPACE_API_KEY;
      try {
        // Construct the URL with query parameters
        const requestUrl = new URL(`${baseUrl}/website-traffic/`);
        requestUrl.searchParams.append('url', url);
        requestUrl.searchParams.append('key', apiKey);
    
        // Perform the fetch request
        const response = await fetch(requestUrl.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 website traffic data:', error);
        return { error: 'An error occurred while getting website traffic data.' };
      }
    };
  • Tool schema definition including name, description, input parameters (url: string, required), for the get_website_traffic tool.
    definition: {
      type: 'function',
      function: {
        name: 'get_website_traffic',
        description: 'Get website traffic data from SEO Review Tools.',
        parameters: {
          type: 'object',
          properties: {
            url: {
              type: 'string',
              description: 'The URL of the website to get traffic data for.'
            }
          },
          required: ['url']
        }
      }
    }
  • Exports the apiTool object which combines the handler function and schema definition for registration.
    const apiTool = {
      function: executeFunction,
      definition: {
        type: 'function',
        function: {
          name: 'get_website_traffic',
          description: 'Get website traffic data from SEO Review Tools.',
          parameters: {
            type: 'object',
            properties: {
              url: {
                type: 'string',
                description: 'The URL of the website to get traffic data for.'
              }
            },
            required: ['url']
          }
        }
      }
    };
    
    export { apiTool };
  • tools/paths.js:2-2 (registration)
    Lists the file path for the get_website_traffic tool in the toolPaths array used for dynamic loading.
    'seo-api-workspace/seo-ap-is-seo-review-tools/get-website-traffic.js',
  • lib/tools.js:7-16 (registration)
    Dynamically imports and registers all tools, including get_website_traffic, by loading apiTool from each module specified in toolPaths.
    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 only states what the tool does ('Get website traffic data') without any context on permissions, rate limits, data freshness, or response format. This is a significant gap for a tool that likely involves external API calls and data retrieval.

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. It's front-loaded with the core purpose and doesn't include unnecessary details, 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 fetching external SEO data, no annotations, and no output schema, the description is incomplete. It lacks crucial details like what traffic data is returned (e.g., visits, sources), error handling, or dependencies on external services, leaving the agent under-informed for effective tool use.

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 schema description coverage is 100%, with the single parameter 'url' clearly documented in the schema. The description doesn't add any parameter-specific details beyond what the schema provides, such as URL format requirements or examples. Baseline 3 is appropriate as the schema handles the parameter documentation adequately.

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 the resource 'website traffic data from SEO Review Tools', making the purpose understandable. However, it doesn't explicitly differentiate from siblings like 'get_authority_scores' or 'get_backlinks', which might also retrieve data from the same source but for different metrics.

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 when to choose this over other sibling tools (e.g., 'get_authority_scores' for authority metrics) or 'post_bulk_website_traffic' for bulk operations, leaving the agent to infer usage from 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