GSC Maestro MCP Server
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| maestro_public_capabilitiesA | Explain what this hosted metrics demo does and cannot do. It cannot access any real Google, Bing, Yandex, or local desktop data. |
| maestro_calculate_ctrA | Calculate clicks divided by impressions, as a percent. All numbers are supplied in the request and must represent the same search source, period and filters. No external queries or stored credentials. |
| maestro_compare_periodsA | Compare two periods using caller-provided click and impression totals and calculate CTR percentage-point changes. No saved search properties, API calls or estimated traffic. |
| maestro_explain_search_metricsA | Explain clicks, impressions, CTR, and average position, including why metrics from different engines should not be combined naively. No account access or source data. |
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 4 tools
The two computational tools (maestro_calculate_ctr, maestro_compare_periods) are clearly distinct, and the two explanatory tools differ in subject matter (demo scope vs. metric definitions). There is mild overlap between maestro_public_capabilities and maestro_explain_search_metrics, since both are descriptive/explanatory with no side effects, but the descriptions make the boundary readable.
All tools share the maestro_ prefix and snake_case naming, which is highly predictable. The only deviation is that three names start with a verb (calculate, compare, explain) while maestro_public_capabilities is a noun phrase, a minor inconsistency.
Four tools is on the thin side but fits a deliberately narrow, credential-free metrics demo: two calculators and two explainers. Each tool earns its place and nothing appears redundant, though the surface leaves little room for variation.
The demo covers CTR calculation and period comparison plus explanatory context, but there is a gap: average position is explained yet no tool computes it, and there is no tool for aggregating or deriving other metrics from supplied clicks/impressions. These are notable but minor omissions given the stated educational scope.