GEO MCP by DigestSEO

Find AI visibility content gaps

get_content_gaps

Read-only

Analyze competitor content advantages to prioritize topics and formats, returning ranked recommendations for closing gaps.

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/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds a meaningful behavioral detail: 'falls back deterministically if AI analysis is unavailable,' which is not in annotations. This goes beyond the baseline and improves transparency.

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 fluff. The core purpose and fallback behavior are front-loaded, followed by a concrete example. Every word earns its place.

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?

Given the simplicity (2 params, output schema present, annotations provided), the description is quite complete. It includes purpose, fallback, and an example. The only minor gap is not stating whether brand_id must refer to an already-tracked brand, but this is not critical for invocation.

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%, so parameters are fully documented. The description's example clarifies usage but adds no semantic nuance beyond the schema. Baseline of 3 is appropriate since the description does not need to compensate for missing schema information.

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?

The description states a specific action ('Prioritize') and a clear resource ('content topics and formats from prompts where competitors beat the brand'). It distinguishes itself from sibling tools like check_visibility and compare_competitors by focusing on content gap prioritization based on competitive disadvantage.

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 description implies usage context (when competitors beat the brand) but does not explicitly compare with alternatives or state when not to use this tool. The example provides a concrete invocation but no exclusions or routing guidance relative to sibling tools.

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

Deploy Server