GEO MCP by DigestSEO

Find AI visibility content gaps

get_content_gaps

Read-only

Prioritizes content topics and formats where competitors beat your brand in AI visibility, closing content gaps. Falls back to deterministic ranking when AI analysis is unavailable.

Instructions

Prioritize content topics and formats from prompts where competitors beat the brand; falls back deterministically if AI analysis is unavailable. Example: brand_id='acme', max_recommendations=5.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`brand_id`	Yes	Tracked brand ID to analyze.
`max_recommendations`	No	Maximum recommendations to return.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`reason`	No
`brand_id`	Yes
`prompt_source`	Yes
`recommendations`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv0.3.23Sep 23, 2026

changedInput schema / properties / brand_id / description

Previous value: -"Stable identifier of the tracked brand to analyze."New value: +"Tracked brand ID to analyze."

changedInput schema / properties / max_recommendations / description

Previous value: -"Maximum number of content recommendations to return."New value: +"Maximum recommendations to return."

Changed4 schema fields changedv0.3.15Sep 20, 2026

addedOutput schema / properties / recommendations / items / additionalProperties
```
Added value: +false
```

addedOutput schema / properties / recommendations / items / properties

Added value: +{
+  "priority": {
+    "maximum": 5,
+    "minimum": 1,
+    "type": "integer"
+  },
+  "rationale": {
+    "type": "string"
+  },
+  "suggested_format": {
+    "enum": [
+      "comparison_page",
+      "listicle",
+      "how_to_guide",
+      "faq_page",
+      "case_study",
+      "pricing_page",
+      "integration_landing_page"
+    ],
+    "type": "string"
+  },
+  "topic": {
+    "type": "string"
+  }
+}

addedOutput schema / properties / recommendations / items / required

Added value: +[
+  "priority",
+  "topic",
+  "rationale",
+  "suggested_format"
+]

addedOutput schema / properties / recommendations / items / type
```
Added value: +"object"
```

First observedv0.3.2Aug 3, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Beyond the readOnly/openWorld annotations, the description discloses a meaningful behavioral trait: a deterministic fallback when AI analysis is unavailable. It also indicates the output is ordered/prioritized, which affects how an agent interprets results. 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?

The description is a single focused sentence followed by a concrete example; no filler or repetition. It front-loads the primary action and includes the fallback behavior economically.

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?

Given the output schema, complete parameter documentation, and annotations, the description supplies everything needed to decide and invoke the tool correctly. The example and fallback note cover the main contextual ambiguities.

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 both parameters are already documented. The description's example (brand_id='acme', max_recommendations=5) reinforces usage but adds little semantic meaning beyond the schema's own descriptions.

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?

Description uses a specific verb ('Prioritize') and identifies the exact resource ('content topics and formats from prompts where competitors beat the brand'). It clearly distinguishes itself from general visibility tools by describing gap-based recommendation output, and the example reinforces scope.

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?

The phrase 'where competitors beat the brand' and the title 'Find AI visibility content gaps' signal when the tool is relevant: competitive gap analysis. However, it does not explicitly name alternatives or state when not to use it, though sibling names like compare_competitors imply related but distinct tools.

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

Deploy Server