Skip to main content
Glama
AKzar1el

GEO MCP by DigestSEO

by AKzar1el
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get AI visibility history

get_visibility_history
Read-only

Retrieve daily or weekly visibility trends with per-engine evidence to track brand citations across AI platforms.

Instructions

Return daily or weekly visibility history with per-engine evidence. Example: brand_id='acme', days=30, granularity='weekly'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoPrevious calendar days to include.
brand_idYesTracked brand ID to inspect.
granularityNoTime bucket for the series.weekly

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysYes
seriesYes
brand_idYes
granularityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.3.23
    • changedInput schema / properties / brand_id / description
      Previous value: -"Stable identifier of the tracked brand to inspect."New value: +"Tracked brand ID to inspect."
    • changedInput schema / properties / days / description
      Previous value: -"Number of previous calendar days to include."New value: +"Previous calendar days to include."
    • changedInput schema / properties / granularity / description
      Previous value: -"Time bucket for the returned visibility series."New value: +"Time bucket for the series."
  2. Changed2 schema fields changedv0.3.15
    • addedOutput schema / properties / series / items / properties / per_engine_evidence
      Added value: +{
+  "additionalProperties": {
+    "additionalProperties": false,
+    "properties": {
+      "brand_mentions": {
+        "type": "number"
+      },
+      "observed_at": {
+        "type": "string"
+      },
+      "usable_prompts": {
+        "type": "number"
+      }
+    },
+    "required": [
+      "brand_mentions",
+      "usable_prompts",
+      "observed_at"
+    ],
+    "type": "object"
+  },
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}
    • changedOutput schema / properties / series / items / required
      Previous value: -[
-  "date",
-  "overall_score",
-  "per_engine"
-]New value: +[
+  "date",
+  "overall_score",
+  "per_engine",
+  "per_engine_evidence"
+]
  3. First observedv0.3.2

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already provide readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that results include per-engine evidence and supports daily/weekly granularity, which is useful context about the nature of the returned data, though not deep behavioral detail.

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 one clear sentence plus a concrete example. It is front-loaded with the core action and every word contributes meaning, with no filler or redundancy.

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?

With a complete schema, annotations, and an output schema present, the description provides sufficient context for a read-only history tool. It lacks only an explicit statement of when to choose this tool over siblings, but that gap is already captured in usage guidelines.

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?

Schema description coverage is 100%, so all parameters already have descriptions. The example in the description reinforces the parameter values but does not add meaning beyond the schema, keeping this at the baseline 3.

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 clearly states a specific verb and resource: 'Return daily or weekly visibility history with per-engine evidence.' This makes the tool's function obvious, but it does not differentiate it from siblings like check_visibility or compare_competitors, so it doesn't reach a 5.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives such as check_visibility or compare_competitors. There are no exclusions or prerequisites mentioned, leaving the agent to infer the appropriate context from the name and description alone.

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

Deploy Server

Other Tools