Skip to main content
Glama
AKzar1el

GEO MCP by DigestSEO

by AKzar1el
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Check AI visibility

check_visibility
Read-only

Retrieve a brand's latest AI visibility snapshot across ChatGPT, Perplexity, Gemini, and more, with scores and winning/losing prompts. Use refresh_brand first for current data.

Instructions

Read the latest stored visibility snapshot, including scores and winning/losing prompts; call refresh_brand first for fresh data. Example: brand_id='acme', engines=['chatgpt','perplexity'].

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
enginesNoEngines to include; omit or pass [] for all stored engines.
brand_idYesTracked brand ID to inspect.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandYes
per_engineYes
refreshed_atYes
overall_scoreYes
top_losing_promptsYes
top_winning_promptsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 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 / engines / description
      Previous value: -"Optional engine filter. If omitted or empty, return results for every engine with stored data."New value: +"Engines to include; omit or pass [] for all stored engines."
  2. Changed1 schema field changedv0.3.19
    • changedInput schema / properties / engines / items / enum
      Previous value: -[
-  "chatgpt",
-  "claude",
-  "perplexity",
-  "gemini",
-  "grok",
-  "ai_overviews"
-]New value: +[
+  "chatgpt",
+  "claude",
+  "perplexity",
+  "gemini",
+  "grok",
+  "ai_overviews",
+  "ai_mode"
+]
  3. Changed1 schema field changedv0.3.18
    • changedInput schema / properties / engines / items / enum
      Previous value: -[
-  "chatgpt",
-  "claude",
-  "perplexity",
-  "gemini",
-  "ai_overviews"
-]New value: +[
+  "chatgpt",
+  "claude",
+  "perplexity",
+  "gemini",
+  "grok",
+  "ai_overviews"
+]
  4. Changed12 schema fields changedv0.3.15
    • addedOutput schema / properties / per_engine / items / additionalProperties
      Added value: +false
    • addedOutput schema / properties / per_engine / items / properties
      Added value: +{
+  "engine": {
+    "type": "string"
+  },
+  "prompts_appeared_in": {
+    "type": "number"
+  },
+  "refreshed_at": {
+    "type": "string"
+  },
+  "score": {
+    "type": "number"
+  },
+  "total_prompts": {
+    "type": "number"
+  }
+}
    • addedOutput schema / properties / per_engine / items / required
      Added value: +[
+  "engine",
+  "score",
+  "prompts_appeared_in",
+  "total_prompts",
+  "refreshed_at"
+]
    • addedOutput schema / properties / per_engine / items / type
      Added value: +"object"
    • addedOutput schema / properties / top_losing_prompts / items / additionalProperties
      Added value: +false
    • addedOutput schema / properties / top_losing_prompts / items / properties
      Added value: +{
+  "competitors_cited": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "prompt": {
+    "type": "string"
+  }
+}
    • addedOutput schema / properties / top_losing_prompts / items / required
      Added value: +[
+  "prompt",
+  "competitors_cited"
+]
    • addedOutput schema / properties / top_losing_prompts / items / type
      Added value: +"object"
    • addedOutput schema / properties / top_winning_prompts / items / additionalProperties
      Added value: +false
    • addedOutput schema / properties / top_winning_prompts / items / properties
      Added value: +{
+  "engines_cited_in": {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  "prompt": {
+    "type": "string"
+  }
+}
    • addedOutput schema / properties / top_winning_prompts / items / required
      Added value: +[
+  "prompt",
+  "engines_cited_in"
+]
    • addedOutput schema / properties / top_winning_prompts / items / type
      Added value: +"object"
  5. Changed3 schema fields changedv0.3.4
    • changedInput schema / properties / engines / description
      Previous value: -"Optional engine filter. If omitted, return results for every engine with stored data."New value: +"Optional engine filter. If omitted or empty, return results for every engine with stored data."
    • removedOutput schema / properties / brand / properties / category / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / brand / properties / category / type
      Added value: +[
+  "string",
+  "null"
+]
  6. First observedv0.3.2

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description aligns with that. It adds useful behavioral context by noting the tool returns a stored snapshot rather than live data and by flagging refresh_brand as a prerequisite for freshness. No contradiction with annotations.

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?

Two sentences with no filler. The primary action is stated first, followed by a necessary prerequisite and a compact example. Every sentence adds value.

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

Completeness5/5

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

For a read-only, two-parameter tool with a full output schema, the description covers the tool's scope, its prerequisite refresh_brand, and a usage example. Nothing essential is missing.

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 the schema already documents both brand_id and engines. The description's example adds a concrete usage pattern (brand_id='acme', engines=['chatgpt','perplexity']) but does not add new semantic meaning beyond the schema.

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

Purpose5/5

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

States a specific verb ('Read'), a precise resource ('latest stored visibility snapshot'), and the key content ('scores and winning/losing prompts'). The description also distinguishes this from refresh_brand by clarifying this reads stored data while that obtains fresh data.

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

Usage Guidelines4/5

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

Gives clear context: this reads the stored snapshot, and if the user wants fresh data, call refresh_brand first. It does not explicitly enumerate when not to use this tool versus get_visibility_history or compare_competitors, but the 'latest stored snapshot' framing makes the intended use obvious.

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