Skip to main content
Glama
PascaleBeier

HitKeep

by PascaleBeier
OverviewSchemaRelated ServersScoreDiscussions
Go
Hybrid

Get HitKeep Site Overview

hitkeep_get_site_overview
Read-onlyIdempotent

Get a site's traffic KPIs, top dimensions, goals, and chart data, with optional comparison period to analyze performance trends.

Instructions

Read aggregate traffic KPIs, top dimensions, goals, chart data, and optional comparison for one site.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoOptional RFC3339 end timestamp. Defaults to now.
fromNoOptional RFC3339 start timestamp. Defaults to 30 days before to.
filtersNoOptional analytics filters.
site_idYesHitKeep site UUID.
compare_toNoOptional RFC3339 comparison end timestamp.
compare_fromNoOptional RFC3339 comparison start timestamp.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYes
fromYes
statsYes
site_idYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed8 schema fields changedv2.13.10
    • changedInput schema / properties / filters / items / properties / type / description
      Previous value: -"Filter type: path, hostname, referrer, referrer_host, device, country, city, provider, asn, browser, language, utm_campaign, utm_content, utm_medium, utm_source, or utm_term."New value: +"Filter type: path, ai_bot, ai_bot_category, ai_source, hostname, referrer, referrer_host, device, country, city, provider, asn, browser, language, utm_campaign, utm_content, utm_medium, utm_source, or utm_term."
    • addedOutput schema / properties / stats / properties / comparison / properties / ai_bot_hits
      Added value: +{
+  "type": "integer"
+}
    • addedOutput schema / properties / stats / properties / comparison / properties / ai_source_visits
      Added value: +{
+  "type": "integer"
+}
    • changedOutput schema / properties / stats / properties / comparison / required
      Previous value: -[
-  "total_pageviews",
-  "unique_sessions",
-  "bounce_rate",
-  "avg_session_duration",
-  "pages_per_session",
-  "chart_data",
-  "utm_campaign_hits",
-  "utm_content_hits",
-  "utm_medium_hits",
-  "utm_source_hits",
-  "utm_term_hits",
-  "goals",
-  "total_conversions"
-]New value: +[
+  "total_pageviews",
+  "unique_sessions",
+  "bounce_rate",
+  "avg_session_duration",
+  "pages_per_session",
+  "chart_data",
+  "ai_bot_hits",
+  "ai_source_visits",
+  "utm_campaign_hits",
+  "utm_content_hits",
+  "utm_medium_hits",
+  "utm_source_hits",
+  "utm_term_hits",
+  "goals",
+  "total_conversions"
+]
    • addedOutput schema / properties / stats / properties / funnels
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "created_at": {
+        "type": "string"
+      },
+      "id": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "site_id": {
+        "type": "string"
+      },
+      "steps": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "type": {
+              "type": "string"
+            },
+            "value": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "type",
+            "value"
+          ],
+          "type": "object"
+        },
+        "type": [
+          "null",
+          "array"
+        ]
+      }
+    },
+    "required": [
+      "id",
+      "site_id",
+      "name",
+      "steps",
+      "created_at"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}
    • addedOutput schema / properties / stats / properties / top_ai_bot_categories
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "name": {
+        "type": "string"
+      },
+      "value": {
+        "type": "integer"
+      }
+    },
+    "required": [
+      "name",
+      "value"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}
    • addedOutput schema / properties / stats / properties / top_ai_bots_by_category
      Added value: +{
+  "additionalProperties": {
+    "items": {
+      "additionalProperties": false,
+      "properties": {
+        "name": {
+          "type": "string"
+        },
+        "value": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "name",
+        "value"
+      ],
+      "type": "object"
+    },
+    "type": [
+      "null",
+      "array"
+    ]
+  },
+  "type": "object"
+}
    • changedOutput schema / properties / stats / required
      Previous value: -[
-  "live_visitors",
-  "total_pageviews",
-  "unique_sessions",
-  "bounce_rate",
-  "avg_session_duration",
-  "pages_per_session",
-  "chart_data",
-  "top_pages",
-  "top_landing_pages",
-  "top_exit_pages",
-  "top_referrers",
-  "top_devices",
-  "top_countries",
-  "top_cities",
-  "top_providers",
-  "top_asns",
-  "top_browsers",
-  "top_ai_bots",
-  "top_ai_sources",
-  "top_languages",
-  "top_utm_campaigns",
-  "top_utm_contents",
-  "top_utm_mediums",
-  "top_utm_sources",
-  "top_utm_terms",
-  "ai_bot_hits",
-  "ai_source_visits",
-  "utm_campaign_hits",
-  "utm_content_hits",
-  "utm_medium_hits",
-  "utm_source_hits",
-  "utm_term_hits",
-  "goals"
-]New value: +[
+  "live_visitors",
+  "total_pageviews",
+  "unique_sessions",
+  "bounce_rate",
+  "avg_session_duration",
+  "pages_per_session",
+  "chart_data",
+  "top_pages",
+  "top_landing_pages",
+  "top_exit_pages",
+  "top_referrers",
+  "top_devices",
+  "top_countries",
+  "top_cities",
+  "top_providers",
+  "top_asns",
+  "top_browsers",
+  "top_ai_bots",
+  "top_ai_bot_categories",
+  "top_ai_sources",
+  "top_languages",
+  "top_utm_campaigns",
+  "top_utm_contents",
+  "top_utm_mediums",
+  "top_utm_sources",
+  "top_utm_terms",
+  "ai_bot_hits",
+  "ai_source_visits",
+  "utm_campaign_hits",
+  "utm_content_hits",
+  "utm_medium_hits",
+  "utm_source_hits",
+  "utm_term_hits",
+  "goals",
+  "funnels"
+]
  2. First observedv2.8.1

TDQS

A3.8/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already provide readOnlyHint=true and idempotentHint=true, and the description's 'Read' aligns with these. The description adds a bit of context regarding the tool's configuration by mentioning 'optional comparison' and 'for one site'. No contradictions exist, and the description is consistent with the safety profile.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence that uses specific terminology ('aggregate traffic KPIs') and avoids fluff. Every word earns its place, providing maximum information in a minimal format.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only tool with an output schema available and all parameters documented, the description is adequate. It clearly defines the tool's scope ('one site') and breadth (KPIs, dimensions, goals, charts). It could add a bit more color on what 'top dimensions' means but is largely complete for the agent to make an informed selection.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema description coverage is 100%, so the parameters are well-documented there. The description does weave in the concept of 'optional comparison,' which loosely connects to the compare_from/compare_to parameters, but it does not add significant new detail beyond what the schema provides; therefore, the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description has a clear verb ('Read') with specific resources ('aggregate traffic KPIs, top dimensions, goals, chart data') and a scope ('for one site'). It clearly communicates the tool's purpose. However, it does not explicitly distinguish itself from sibling tools by naming any alternatives, though the enumerated data types and 'one site' scope provide decent differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage guidance is only implied through the data types listed ('KPIs, dimensions, goals'), suggesting this is the go-to overview tool. There are no explicit when-to-use vs. alternatives, nor any exclusions, despite a long list of sibling tools where such guidance would be beneficial. The agent has to infer the tool's role is the broad overview.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PascaleBeier/hitkeep'

If you have feedback or need assistance with the MCP directory API, please join our Discord server