Sealmetrics MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SEALMETRICS_EMAIL | No | Email for login (alternative to token) | |
| SEALMETRICS_PASSWORD | No | Password for login (alternative to token) | |
| SEALMETRICS_API_TOKEN | No | Your Sealmetrics API token (recommended) | |
| SEALMETRICS_ACCOUNT_ID | No | Default account ID for queries |
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": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_accountsB | Get list of Sealmetrics accounts available to the authenticated user |
| get_traffic_dataB | Get traffic/acquisition data from Sealmetrics. Answers questions like 'How much traffic from SEO yesterday?' or 'Show me Google Ads performance this month' |
| get_conversionsB | Get conversion/sales data from Sealmetrics. Answers questions like 'How many sales this month?' or 'Show conversions from Google Ads yesterday' |
| get_microconversionsB | Get microconversion data (add-to-cart, signups, etc.) from Sealmetrics. Answers questions like 'How many add to carts from Google Ads yesterday?' |
| get_funnel_dataC | Get funnel analysis showing progression through conversion stages |
| get_roas_evolutionC | Get ROAS (Return on Ad Spend) evolution over time with revenue, conversions, and clicks |
| get_pages_performanceB | Get page performance metrics including views and entry pages. Can filter by content groups to analyze specific sections of your site (e.g., 'Blog Content', 'Product Catalog', 'Support Pages') |
| generate_conversion_pixelC | Generate a Sealmetrics tracking pixel for conversions or microconversions, ready for Google Tag Manager |
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 8 tools
Most tools have distinct purposes targeting specific analytics domains like conversions, traffic, funnels, and pages. However, 'get_conversions' and 'get_microconversions' could cause some confusion as microconversions are a subset of conversions, though descriptions clarify the difference.
All tools follow a consistent verb_noun pattern with 'get_' or 'generate_' prefixes, using snake_case throughout. This predictable naming makes it easy for agents to understand and select tools without ambiguity.
With 8 tools, this server is well-scoped for analytics and tracking purposes. Each tool covers a distinct aspect of the domain, such as accounts, conversions, traffic, and performance, without being overly sparse or bloated.
The tool set covers core analytics workflows including data retrieval for conversions, traffic, funnels, and ROAS, plus account management and pixel generation. A minor gap is the lack of update or configuration tools for settings, but agents can still perform most common tasks effectively.