Skip to main content
Glama
fetchSERP

FetchSERP MCP Server

Official
by fetchSERP
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

get_webpage_ai_analysis

Analyze a web page using AI-generated insights by providing a URL and specific prompt. Designed for SEO analysis, SERP data extraction, keyword research, and web scraping tasks.

Instructions

Analyze a web page with AI

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesThe prompt to use for the analysis
urlYesThe url to analyze

Implementation Reference

  • index.js:673-674 (handler)
    Handler implementation for the 'get_webpage_ai_analysis' tool. It calls the FetchSERP API endpoint '/api/v1/web_page_ai_analysis' using the shared makeRequest method with the tool arguments.
    case 'get_webpage_ai_analysis':
  return await this.makeRequest('/api/v1/web_page_ai_analysis', 'GET', args, null, token);
  • index.js:444-461 (schema)
    Schema definition and registration for the 'get_webpage_ai_analysis' tool, specifying the input parameters 'url' and 'prompt' as required.
    {
  name: 'get_webpage_ai_analysis',
  description: 'Analyze a web page with AI',
  inputSchema: {
    type: 'object',
    properties: {
      url: {
        type: 'string',
        description: 'The url to analyze',
      },
      prompt: {
        type: 'string',
        description: 'The prompt to use for the analysis',
      },
    },
    required: ['url', 'prompt'],
  },
},

Tool Definition Quality

C2.7/5.0
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. It mentions 'with AI' but doesn't disclose behavioral traits like what AI model is used, rate limits, authentication needs, output format, or potential costs. This leaves significant gaps for an AI agent to understand how the tool behaves beyond basic functionality.

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 extremely concise at just four words, with zero wasted language. It's front-loaded with the core action and resource, making it easy to parse quickly despite its brevity.

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 AI analysis tools and lack of annotations or output schema, the description is incomplete. It doesn't explain what the analysis returns, how the AI is applied, or any constraints. For a tool with two parameters and no structured output documentation, this minimal description leaves too many unanswered questions.

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 both parameters (url, prompt) clearly documented in the schema. The description adds no additional meaning about parameters beyond what's in the schema, so it meets the baseline 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.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Analyze a web page with AI' states the basic action (analyze) and resource (web page), but it's vague about what type of analysis is performed. It doesn't distinguish this tool from sibling tools like 'get_webpage_seo_analysis' or 'get_moz_analysis', leaving ambiguity about the specific purpose.

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 multiple sibling tools for web analysis (e.g., get_webpage_seo_analysis, get_moz_analysis, scrape_webpage), there's no indication of what makes this AI analysis unique or when it's preferred over other options.

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