Skip to main content
Glama
AKzar1el

GEO MCP by DigestSEO

by AKzar1el
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get AI citation evidence

get_citations
Read-only

Retrieve brand citation evidence and top source domains from tracked engines over a chosen period.

Instructions

Return stored brand citation evidence plus the top engine-native source domains across the same tracked-prompt window. Example: brand_id='acme', days=14, engine='perplexity'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoPrevious days to search.
engineNoEngine to filter by; omit for all engines.
brand_idYesTracked brand ID to inspect.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysYes
engineYes
brand_idYes
citationsYes
top_sourcesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.3.24
    • addedOutput schema / properties / top_sources
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "citation_count": {
+        "type": "number"
+      },
+      "domain": {
+        "type": "string"
+      },
+      "engines": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "is_brand_domain": {
+        "type": "boolean"
+      },
+      "prompt_count": {
+        "type": "number"
+      },
+      "sample_url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "domain",
+      "citation_count",
+      "prompt_count",
+      "engines",
+      "sample_url",
+      "is_brand_domain"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • changedOutput schema / required
      Previous value: -[
-  "brand_id",
-  "days",
-  "engine",
-  "citations"
-]New value: +[
+  "brand_id",
+  "days",
+  "engine",
+  "top_sources",
+  "citations"
+]
  2. 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 days from which to return citations."New value: +"Previous days to search."
    • changedInput schema / properties / engine / description
      Previous value: -"Optional engine filter for the citation events."New value: +"Engine to filter by; omit for all engines."
  3. Changed1 schema field changedv0.3.19
    • changedInput schema / properties / engine / enum
      Previous value: -[
-  "chatgpt",
-  "claude",
-  "perplexity",
-  "gemini",
-  "grok",
-  "ai_overviews"
-]New value: +[
+  "chatgpt",
+  "claude",
+  "perplexity",
+  "gemini",
+  "grok",
+  "ai_overviews",
+  "ai_mode"
+]
  4. Changed1 schema field changedv0.3.18
    • changedInput schema / properties / engine / enum
      Previous value: -[
-  "chatgpt",
-  "claude",
-  "perplexity",
-  "gemini",
-  "ai_overviews"
-]New value: +[
+  "chatgpt",
+  "claude",
+  "perplexity",
+  "gemini",
+  "grok",
+  "ai_overviews"
+]
  5. Changed4 schema fields changedv0.3.4
    • removedOutput schema / properties / citations / items / properties / cited_url / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / citations / items / properties / cited_url / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / engine / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / engine / type
      Added value: +[
+  "string",
+  "null"
+]
  6. First observedv0.3.2

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, covering the safety profile. The description adds useful context that it returns stored evidence and top source domains over a tracked-prompt window, but it does not clarify pagination, response shape, or the definition of 'tracked-prompt window'.

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 definition is two sentences with no filler: the first states the return scope, the second gives a concrete usage example. It is appropriately sized and front-loaded.

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 simple read-only tool with full schema coverage, an output schema, and safety annotations, the description plus schema are largely sufficient. The only minor gap is that domain-specific terms like 'tracked-prompt window' and 'engine-native source domains' are not defined, but the example helps ground them.

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 coverage is 100%, with clear descriptions for brand_id, days, and engine, including an enum and default. The description adds only an illustrative example, not new parameter semantics beyond what the schema already provides.

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 states a specific verb ('Return') and resource ('stored brand citation evidence plus the top engine-native source domains'), which clearly identifies what the tool does. It is distinct enough from siblings like get_visibility_history, though it does not explicitly call out the 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?

The example invocation (brand_id='acme', days=14, engine='perplexity') implies when the tool is useful, and the term 'citations' suggests its niche among sibling tools. However, there is no explicit guidance on when to prefer it over alternatives like get_visibility_history or compare_competitors.

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