mcp-activeview
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ACTIVEVIEW_API_KEY | Yes | Your ActiveView API key in token:secret format | |
| ACTIVEVIEW_NETWORK_CODE | No | Optional default network code for reports |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_price_rulesA | Get all price (pricing) rules configured for a site. Returns an array of rule objects with fields such as ad_unit, country, device, ecpm, impressions, match_rate, desired_match_rate, revenue, rule, state and utm_source. |
| get_report_by_domainA | Metrics report for a single domain (same metrics used by the pricing service). Returns per-request_uri rows with ad_unit, country, device, ecpm, impressions, eligible_ad_requests, match_rate, responses_served, revenue and utm_source. |
| get_kvp_report_by_domainB | Key-value-pair (KVP) metrics for a domain, grouped by a GAM key. Returns rows keyed by |
| get_session_kvp_report_by_domainB | Session-based KVP report for a domain (sessions data from Snowflake). Returns rows with COUNTRY_CODE, COUNTRY_NAME, KEY, VALUE, RECORDED_DATE and TOTAL, filtered by the given key. |
| get_custom_gam_report_by_domainA | Custom GAM report for a domain with caller-chosen dimensions and metrics. Availability of dimension/metric combinations matches GAM itself; combos that GAM cannot report will also fail here. Revenue fields are in micros. |
| get_report_by_networkA | Metrics report across a whole network, optionally filtered to some domains. Same row shape as get_report_by_domain. |
| get_kvp_report_by_networkB | KVP metrics across a network, grouped by a GAM key. Revenue in micros. |
| get_custom_gam_report_by_networkA | Custom GAM report across a network with caller-chosen dimensions and metrics. Same constraints as get_custom_gam_report_by_domain. Revenue fields in micros. |
| list_redirect_domainsA | List redirect domains created in the web interface, each with its paths. Returns {"redirectDomains": [{id, name, createdAt, redirectPaths:[{id, path}]}]}. Returns an empty list if none exist. |
| get_redirect_pathA | Get details of a specific redirect path, including its current mappings. |
| get_redirect_path_mappingsA | Get the traffic-split mappings (url + percentage) for a redirect path. |
| get_redirect_path_mapping_logsB | Get the change logs (CREATE/UPDATE/DELETE) for a redirect path's mappings. |
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 12 tools
Each tool targets a distinct reporting or redirect management operation. Custom GAM reports, KVP reports, session reports, price rules, and redirect paths are all clearly separated, with no overlapping purposes.
Most tools follow a 'get_<noun>_by_<scope>' pattern (e.g., get_custom_gam_report_by_domain) or 'list_<noun>' (e.g., list_redirect_domains). The pattern is consistent snake_case, though get_price_rules deviates slightly by not including a scope.
With 12 tools covering multiple areas (reports, redirects, pricing rules), the count is well-scoped for a read-only dashboard server. Each tool has a distinct purpose and none seem extraneous.
The tool surface covers the main read operations for GAM reports, redirect paths, and pricing rules. Missing write operations (create/update/delete) are likely intentional given the 'view' nature, but could be considered a minor gap for full lifecycle management.