Skip to main content
Glama
fetchSERP

FetchSERP MCP Server

Official
by fetchSERP

get_webpage_seo_analysis

Analyze the SEO performance of any webpage to identify optimization opportunities and improve search engine visibility. Input the URL to receive actionable insights.

Instructions

Get SEO analysis for a given url

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe url to analyze

Implementation Reference

  • The handler function for the 'get_webpage_seo_analysis' tool. It calls the shared makeRequest method to perform a GET request to the FetchSERP API endpoint '/api/v1/web_page_seo_analysis' with the tool arguments.
    case 'get_webpage_seo_analysis':
      return await this.makeRequest('/api/v1/web_page_seo_analysis', 'GET', args, null, token);
  • index.js:522-535 (registration)
    Registration of the 'get_webpage_seo_analysis' tool in the listTools response, including its name, description, and input schema.
    {
      name: 'get_webpage_seo_analysis',
      description: 'Get SEO analysis for a given url',
      inputSchema: {
        type: 'object',
        properties: {
          url: {
            type: 'string',
            description: 'The url to analyze',
          },
        },
        required: ['url'],
      },
    },
  • Input schema definition for the 'get_webpage_seo_analysis' tool, specifying the required 'url' parameter.
    inputSchema: {
      type: 'object',
      properties: {
        url: {
          type: 'string',
          description: 'The url to analyze',
        },
      },
      required: ['url'],
    },
  • Shared helper method 'makeRequest' used by all tools, including 'get_webpage_seo_analysis', to make authenticated HTTP requests to the FetchSERP API.
    async makeRequest(endpoint, method = 'GET', params = {}, body = null, token = null) {
      const fetchserpToken = token || process.env.FETCHSERP_API_TOKEN;
      
      if (!fetchserpToken) {
        throw new McpError(
          ErrorCode.InvalidRequest,
          'FETCHSERP_API_TOKEN is required'
        );
      }
    
      const url = new URL(`${API_BASE_URL}${endpoint}`);
      
      // Add query parameters for GET requests
      if (method === 'GET' && Object.keys(params).length > 0) {
        Object.entries(params).forEach(([key, value]) => {
          if (value !== undefined && value !== null) {
            if (Array.isArray(value)) {
              value.forEach(v => url.searchParams.append(`${key}[]`, v));
            } else {
              url.searchParams.append(key, value.toString());
            }
          }
        });
      }
    
      const fetchOptions = {
        method,
        headers: {
          'Authorization': `Bearer ${fetchserpToken}`,
          'Content-Type': 'application/json',
        },
      };
    
      if (body && method !== 'GET') {
        fetchOptions.body = JSON.stringify(body);
      }
    
      const response = await fetch(url.toString(), fetchOptions);
      
      if (!response.ok) {
        const errorText = await response.text();
        throw new McpError(
          ErrorCode.InternalError,
          `API request failed: ${response.status} ${response.statusText} - ${errorText}`
        );
      }
    
      return await response.json();
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden but lacks behavioral details. It doesn't disclose whether this is a read-only operation, if it requires authentication, rate limits, what 'SEO analysis' entails (e.g., metrics, reports), or potential side effects. The description is minimal and fails to compensate for the absence of 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, efficient sentence with zero waste: 'Get SEO analysis for a given url'. It is front-loaded and appropriately sized for its purpose, making it easy to parse without unnecessary elaboration.

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 analysis and the lack of annotations and output schema, the description is incomplete. It doesn't explain what the analysis includes (e.g., keywords, backlinks, performance metrics), the return format, or error handling. For a tool with no structured output and rich sibling context, more detail is needed to be fully helpful.

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%, with the single parameter 'url' documented as 'The url to analyze'. The description adds no additional meaning beyond this, such as URL format requirements or validation rules. Baseline 3 is appropriate since the schema adequately covers the parameter semantics.

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 tool's purpose: 'Get SEO analysis for a given url' specifies the verb ('Get'), resource ('SEO analysis'), and target ('url'). It distinguishes from some siblings like 'get_backlinks' or 'get_domain_info' by focusing on webpage-level SEO, though it doesn't explicitly differentiate from 'get_webpage_ai_analysis' which might overlap.

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?

No guidance is provided on when to use this tool versus alternatives. With many sibling tools like 'get_moz_analysis', 'get_serp_results', and 'get_webpage_ai_analysis', the description offers no context on selection criteria, prerequisites, or exclusions, leaving usage ambiguous.

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

Related 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/fetchSERP/fetchserp-mcp-server-node'

If you have feedback or need assistance with the MCP directory API, please join our Discord server