Skip to main content
Glama
fetchSERP

FetchSERP MCP Server

Official
by fetchSERP
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

get_serp_ai_mode

Retrieve SERP AI Overview and AI Mode responses for a query in under 30 seconds. Use this tool to analyze search results, SEO data, and keyword insights efficiently.

Instructions

Get SERP with AI Overview and AI Mode response. Returns AI overview and AI mode response for the query. Less reliable than the 2-step process but returns results in under 30 seconds.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryNoThe country to search from. Default: usus
queryYesThe query to search

Implementation Reference

  • index.js:664-665 (handler)
    Handler implementation for 'get_serp_ai_mode' tool. It proxies the tool call to the FetchSERP API endpoint '/api/v1/serp_ai_mode' using the shared makeRequest method with GET method and tool arguments.
    case 'get_serp_ai_mode':
  return await this.makeRequest('/api/v1/serp_ai_mode', 'GET', args, null, token);
  • index.js:386-404 (registration)
    Tool registration in the ListTools response, including name, description, and input schema definition for 'get_serp_ai_mode'.
    {
  name: 'get_serp_ai_mode',
  description: 'Get SERP with AI Overview and AI Mode response. Returns AI overview and AI mode response for the query. Less reliable than the 2-step process but returns results in under 30 seconds.',
  inputSchema: {
    type: 'object',
    properties: {
      query: {
        type: 'string',
        description: 'The query to search',
      },
      country: {
        type: 'string',
        description: 'The country to search from. Default: us',
        default: 'us',
      },
    },
    required: ['query'],
  },
},

Tool Definition Quality

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: reliability concerns ('Less reliable than the 2-step process') and performance characteristics ('returns results in under 30 seconds'). However, it doesn't cover other important aspects like error handling, rate limits, authentication needs, or what 'AI Mode response' entails.

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 and front-loaded: three sentences with zero waste. The first sentence states the core purpose, the second clarifies the return values, and the third provides crucial usage guidance. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations and no output schema, the description is moderately complete for a tool with 2 parameters. It covers purpose, return values, and trade-offs, but lacks details about output structure, error conditions, or deeper behavioral context. For a tool involving AI features and reliability concerns, more completeness would be beneficial.

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 already fully documents both parameters (query and country). The description doesn't add any parameter-specific information beyond what's in the schema, such as explaining how the country affects AI responses or query formatting. Baseline 3 is appropriate when schema does the heavy lifting.

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 SERP with AI Overview and AI Mode response' specifies the verb (get) and resource (SERP with AI features). It distinguishes from siblings like get_serp_html or get_serp_results by emphasizing AI-specific outputs, though it doesn't explicitly name alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use this tool: 'Less reliable than the 2-step process but returns results in under 30 seconds' implies a trade-off between speed and reliability. It doesn't explicitly name the alternative 2-step process or specify when-not scenarios, but the guidance is practical.

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