Skip to main content
Glama
RichardDillman

Googlebot Simulator MCP

by RichardDillman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
simulate_googlebotA

Simulate Googlebot crawling a page and capture analytics events.

This tool:

  • Uses authentic Googlebot user-agent strings

  • Simulates Googlebot's idle detection behavior (requestIdleCallback)

  • Intercepts and captures network requests matching your pattern

  • Returns detailed timing, events captured, and optional screenshots

Use this to verify:

  • Analytics pageview events fire correctly for bots

  • Bot detection is working (e.g., page_viewed vs page_viewed_bot)

  • Content is rendered correctly at the "idle" state

  • Timing of event firing relative to page load

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly distinct by default.

Naming Consistency5/5

The single tool name 'simulate_googlebot' follows a clear verb_noun pattern and is descriptive. With only one tool, there are no naming inconsistencies.

Tool Count3/5

One tool is on the low end, but it is well-scoped to a specific use case (simulating Googlebot). It feels slightly thin but not inappropriate for its narrow domain.

Completeness4/5

The tool covers the main aspects of simulating Googlebot crawling (user-agent, idle detection, event capture, timing, screenshots). No obvious gaps for its stated purpose, though it is a single tool.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources