opengsc
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENGSC_CLIENT_ID | No | OAuth client ID, provided instead of `client_secret.json`. | |
| OPENGSC_CLIENT_SECRET | No | OAuth client secret, provided instead of `client_secret.json`. | |
| OPENGSC_REFRESH_TOKEN | No | Refresh token printed by `opengsc auth` as `OPENGSC_REFRESH_TOKEN=...`. Set that variable (plus the OAuth client) to run without a `token.json` file, for example in a container. Treat it like a password. | |
| OPENGSC_SERVICE_ACCOUNT_FILE | No | Path to a service account JSON key. Then add the service account's email as a user of your property in Search Console (Settings → Users and permissions). No browser login needed, good for servers. |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sitesA | List Search Console properties the account can read, with permission level. Returns TSV: site_urlpermission_level. Use the site_url values as-is for the site_url argument of the other tools. |
| search_analyticsA | Query search analytics for one property. site_url: property from list_sites. start_date/end_date: YYYY-MM-DD (default: last 28 days ending 3 days ago). dimensions: subset of query, page, country, device, date, searchAppearance. filters: list of {dimension, operator, expression} with operators equals, notEquals, contains, notContains, includingRegex, excludingRegex. search_type: web, image, video, news, discover, googleNews. data_state: final or all. row_limit: 1..25000; start_row: pagination offset. Returns TSV rows plus a metadata block (date range, rows returned, more_may_exist: true when rows == row_limit, so paginate with start_row). |
| list_sitemapsB | List submitted sitemaps for one property with status and counts. Top-level fields are TSV; the nested contents array is compact JSON exactly as the API sends it. |
| inspect_urlA | Run URL Inspection for one URL inside one property. Returns the result as compact JSON exactly as the API sends it: index status, coverage, canonical, last crawl, mobile usability if present. Counts against Google's 2,000/day per-property quota. |
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
Each tool maps to a distinct GSC resource/action: list_sites (properties), search_analytics (performance data), list_sitemaps (sitemap status), and inspect_url (per-URL indexing). There is no meaningful overlap in purpose, so an agent can select the right tool unambiguously.
All four tools use snake_case verb_noun form (list_sites, search_analytics, list_sitemaps, inspect_url), which is highly predictable. The only minor deviation is the mix of verbs (list/search/inspect) rather than a single repeated prefix, though each verb matches its action.
Four tools cover the core read surface of Search Console cleanly with no filler. It sits at the thin end of the well-scoped range but each tool clearly earns its place.
The set covers the primary read operations (properties, analytics, sitemaps, URL inspection) well. Write operations like adding/deleting sites or submitting sitemaps are absent, but these are minor gaps for a read-oriented analysis server.