dotTide
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOTTIDE_GITHUB_TOKEN | No | A read-only GitHub token to avoid the 60 anonymous requests per hour per IP limit. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sitesA | Every configured site, which key covers it, and whether Search Console and GA4 access works at the moment of the call. |
| search_queriesA | Search Console clicks, impressions, CTR (percent) and average position, by "query" or
"page". Dates are YYYY-MM-DD; without them the range is the last |
| page_queriesA | The queries that bring people to one page (full URL), with the page's own totals and
|
| trafficB | GA4 sessions by source and medium, plus AI assistant referrals (ChatGPT, Perplexity, Copilot, Gemini, Claude and others) totalled separately. Each assistant lists the landing_pages its visits started on, most sessions first. Only for sites with GA4. |
| store_statsC | Live public store numbers that need no keys: WordPress.org plugins (installs, rating, downloads last 7 days), Firefox Add-ons (daily users, ratings), GitHub stars. |
| opportunitiesA | What to work on next for a site, from Search Console: queries in striking distance (position 8 to 20, by impressions), pages and queries that lost the most clicks against the previous period, pages and queries whose average position dropped the most (slipping_pages, slipping_queries, with min_impressions in both periods), and page-one queries whose CTR is under half the site's own median for that position. When low_ctr is empty because no position band has three queries, low_ctr_note says so and low_ctr_band_counts gives each band's count. Every item carries its numbers. Same date rules and filters as search_queries, except Discover and Google News, which have no query rows. |
| competing_pagesA | Queries where two or more pages of the site each get at least |
| index_healthA | Is the site healthy in Google's index? Every sitemap Search Console knows (errors,
warnings, when Google last read it, URLs submitted) and the index status of the top |
| core_web_vitalsA | Core Web Vitals for a page (default: the site's home page) from PageSpeed Insights. page_field and site_field hold real-user 75th-percentile LCP, INP and CLS with Google's good / needs improvement / poor rating, when Google has enough visits; lab holds one Lighthouse run (performance score, LCP, CLS, TBT, FCP, Speed Index). strategy is "mobile" or "desktop". One run takes 10 to 30 seconds. |
| bing_queriesB | Bing Webmaster Tools clicks, impressions and average position by query, plus site totals, for a range. Bing feeds Copilot. Needs a [bing] key in the site's profile. Bing updates these numbers about once a week. |
| discoverB | Every Search Console property and GA4 web stream the key can read, matched by domain,
with ready-to-paste [[sites]] blocks for any site not in a profile yet. Each block has a
commented-out brand_terms suggestion from the domain name. Reads only; the user adds the
blocks with |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| weekly_review | Week-over-week review of every site, or one site: clicks, top movers, AI referrals, Bing where it's set up, and store changes, ending with the most useful thing to do this week. |
| what_to_work_on | The three changes with the most to gain on a site, from its opportunities. |
| index_check | Anything keeping a site's pages out of Google, in plain words. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Most tools target distinct resources, but search_queries (which accepts a 'page' dimension) and page_queries overlap significantly—an agent could reasonably reach for either when asked for a page's queries. bing_queries vs search_queries is clearer due to the source distinction, and the analytic tools (opportunities, competing_pages, index_health, core_web_vitals) are well separated.
Nearly all names are lowercase snake_case noun phrases (bing_queries, search_queries, core_web_vitals, index_health, competing_pages). Minor deviation: several single-word nouns (sites, traffic, opportunities) and one verb (discover) break the compound pattern slightly, but the set remains readable and predictable.
Eleven tools sit squarely in the well-scoped range, and each covers a distinct slice (per-source queries, GA4 traffic, discovery, store stats, opportunity analysis, cannibalization, index health, CWV). No obvious padding or redundancy.
The surface covers the core read-only SEO analytics lifecycle: discovery, traffic sources, keyword/query performance across GSC and Bing, index/sitemap health, and Core Web Vitals, plus derived opportunity analysis. Gaps exist (no backlink analysis, no sitemap submission—explicitly read-only by design), but these are minor workarounds.