gsc-coverage
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_APPLICATION_CREDENTIALS | No | Path to a Google service account JSON key. If omitted, Application Default Credentials from gcloud auth application-default login are used. |
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 |
|---|---|
| list_sitesA | List the Search Console properties these credentials can read, with permission level. |
| search_analyticsA | Pull Search Console performance rows, paging past the 25,000-row API cap until Google has no more rows (or maxRows is hit). Every response includes a coverage block: rows returned, pages fetched, whether the pull was truncated, property totals for the same window, and the share of clicks and impressions the rows account for. Read the coverage block and its notes before drawing conclusions. Large pulls are written to a CSV/JSON file and only a preview comes back inline. |
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 2 tools
The two tools target completely different resources: list_sites enumerates accessible properties, while search_analytics pulls performance rows with coverage metadata. There is no plausible way to confuse one for the other, and the descriptions make the boundary explicit.
Both names follow the same snake_case verb_noun convention (list_sites, search_analytics), with clear resource nouns. The pattern is predictable and would extend naturally if more tools were added.
Two tools is thin for a Search Console surface, even a narrowly scoped one; a single discovery tool plus a single query tool leaves little room for workflow support. It is defensible for a read-only, coverage-focused server, but sits at the borderline of the 1-2 tool range.
The core read path is covered end to end: discover properties, then pull paged performance data with totals and truncation reporting so agents can reason about coverage. Minor gaps exist around adjacent Search Console operations (e.g. sitemaps, URL inspection, or dimension/metric discovery), but nothing that blocks the stated purpose.