Puppeteer+ MarTech
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| puppeteer_navigateC | Navigate to a URL |
| puppeteer_screenshotB | Take a screenshot of the current page or a specific element |
| find-marketing-technologiesC | Get a high-level overview of all marketing technologies on a webpage |
| analyze-analytics-platformsC | Deep dive into analytics platforms (GA4, UA, Adobe Analytics, etc.) on a webpage |
| detect-ad-pixelsC | Focus on advertising platforms (Facebook, TikTok, etc.) on a webpage |
| identify-tag-managersB | Analyze tag management systems (GTM, Tealium, etc.) on a webpage |
| track-marketing-beaconsC | Analyze network requests for tracking and marketing activities |
| highlight-marketing-toolsB | Take a screenshot with marketing technologies visually highlighted |
| scan-marketing-stackC | Comprehensive analysis of all marketing and analytics technologies on a webpage |
| visualize-marketing-techB | Take a screenshot with detailed marketing technologies visually highlighted |
| parse-analytics-beaconsB | Capture and parse Adobe Analytics and Experience Platform beacons on a webpage |
| audit-seoC | Analyze SEO metadata and structure on a webpage |
| check-page-metadataB | Analyze meta tags, titles, and descriptions on a webpage |
| evaluate-page-structureB | Analyze URL structure, headings hierarchy, and page organization |
| extract-schema-markupB | Analyze JSON-LD, microdata, and schema.org markup on a webpage |
| audit-image-alt-textB | Audit image alt text on a webpage for accessibility and SEO compliance |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Several tools have nearly identical purposes: highlight-marketing-tools vs visualize-marketing-tech only differ by 'detailed', and find-marketing-technologies vs scan-marketing-stack both give overviews. track-marketing-beacons and parse-analytics-beacons also overlap significantly. Agents will struggle to choose the right tool.
Most tools use lowercase with hyphens (audit-seo, find-marketing-technologies), but two use underscores (puppeteer_navigate, puppeteer_screenshot). The verb-noun pattern is present but the separators are inconsistent, creating a mixed style.
16 tools is at the high end of the acceptable range and feels heavy because many tools are redundant. However, it's not an extreme count for a MarTech analysis server.
The set covers major MarTech analysis areas: SEO, marketing technology detection, analytics platforms, ad pixels, tag managers, and beacons. Minor gaps exist (e.g., no generic content extraction), but core workflows are well supported.