DDMarketer

This week's highest-intent gaps

get_top_gaps

Read-only

Return the highest commercial-intent validated gaps from the past week, across all categories. Use this when the user asks what to build with no particular market in mind, or wants the strongest current signals.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Max gaps to return (1-25, default 10).
`category`	No	Optional exact category filter.

Output Schema

TableJSON Schema

Name	Required	Description
`gaps`	Yes
`loose`	No	True when no gap matched all your terms and these are loosely related instead. Not validation.
`scope`	No	get_top_gaps only: 'weekly' = the source complaints are from the last 7 days; 'all-time' = the week was empty, so these are the highest-intent gaps overall.
`total`	Yes	Exact number of gaps matching the query in the corpus, NOT the length of the list above -- the list is capped by `limit`. Quote this, not gaps.length, when telling the user how much demand there is.
`weekOf`	No	get_top_gaps only, present with scope 'weekly': the UTC date the 7-day window opened (YYYY-MM-DD).
`hasMore`	Yes	True when more gaps matched than the list carries (the query is limit-clamped). Offer to narrow or paginate rather than implying the list is everything.
`dossierUrl`	Yes
`upgradeUrl`	No	Present only when the caller's plan does not include full dossiers: the page that unlocks them. Surface it when the user wants depth the teaser does not have.
`attribution`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedSep 28, 2026

addedInput schema / properties / limit / default
```
Added value: +10
```
addedInput schema / properties / limit / maximum
```
Added value: +25
```
addedInput schema / properties / limit / minimum
```
Added value: +1
```

addedOutput schema / properties / hasMore

Added value: +{
+  "description": "True when more gaps matched than the list carries (the query is limit-clamped). Offer to narrow or paginate rather than implying the list is everything.",
+  "type": "boolean"
+}

addedOutput schema / properties / scope

Added value: +{
+  "description": "get_top_gaps only: 'weekly' = the source complaints are from the last 7 days; 'all-time' = the week was empty, so these are the highest-intent gaps overall.",
+  "enum": [
+    "weekly",
+    "all-time"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / total / description

Added value: +"Exact number of gaps matching the query in the corpus, NOT the length of the list above -- the list is capped by `limit`. Quote this, not gaps.length, when telling the user how much demand there is."

addedOutput schema / properties / weekOf

Added value: +{
+  "description": "get_top_gaps only, present with scope 'weekly': the UTC date the 7-day window opened (YYYY-MM-DD).",
+  "type": "string"
+}

changedOutput schema / required

Previous value: -[
-  "gaps",
-  "total",
-  "dossierUrl",
-  "attribution"
-]New value: +[
+  "gaps",
+  "total",
+  "hasMore",
+  "dossierUrl",
+  "attribution"
+]

Changed1 schema field changedSep 4, 2026

addedOutput schema / properties / upgradeUrl

Added value: +{
+  "description": "Present only when the caller's plan does not include full dossiers: the page that unlocks them. Surface it when the user wants depth the teaser does not have.",
+  "type": "string"
+}

Changed2 schema fields changedSep 2, 2026

addedOutput schema / properties / gaps / items / properties / publicUrl

Added value: +{
+  "description": "Public page for this gap, readable with no account: the complaint, the scores, and how it compares in its category. Offer this first.",
+  "type": "string"
+}

changedOutput schema / properties / gaps / items / properties / url / description

Previous value: -"Link to give the user for this specific gap."New value: +"Link to this gap's full dossier. Requires a free account; anonymous visitors are redirected to signup and land back on THIS gap."

Changed2 schema fields changedAug 29, 2026
- addedOutput schema / properties / gaps / items / properties / category / description
```
Added value: +"Broad product category, e.g. 'E-commerce' or 'DevTools'. Reusable as the category filter."
```
- addedOutput schema / properties / gaps / items / properties / title / description
```
Added value: +"The opportunity, phrased as what is missing."
```

Changed1 schema field changedAug 28, 2026

addedOutput schema / properties / gaps / items / properties / url

Added value: +{
+  "description": "Link to give the user for this specific gap.",
+  "type": "string"
+}

Changed2 schema fields changedAug 28, 2026

removedOutput schema / properties / gaps / items / properties / trending
```
Removed value: -{
-  "type": "boolean"
-}
```

changedOutput schema / properties / gaps / items / required

Previous value: -[
-  "id",
-  "title",
-  "category",
-  "commercialIntent",
-  "confidence",
-  "trending"
-]New value: +[
+  "id",
+  "title",
+  "category",
+  "commercialIntent",
+  "confidence"
+]

First observedAug 14, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, and the title restates the weekly/high-intent framing. The description adds the notion of a curated 'validated' set, which is real behavioral context beyond the annotations, but says nothing about ordering guarantees, how many signals exist, or what 'validated' means operationally.

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 tight sentences: the first defines the return set, the second gives the usage trigger, with no filler or restated schema text. Every clause carries information for tool selection.

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 annotations covering safety, a rich output schema, and 100% parameter coverage in the schema, the description supplies what the agent still needs: scope (past week, all categories) and the usage trigger. A brief mention of how it relates to search_gaps/validate_idea would complete the picture.

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 `limit` (range and default) and `category` (exact filter) are already fully documented in the schema, and the output schema exists. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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?

States a specific verb and resource ('return the highest commercial-intent validated gaps') plus a precise scope ('past week, across all categories'). It implicitly distinguishes itself from search_gaps by emphasizing no market filter, but never names the sibling explicitly, so the agent must infer the boundary.

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?

'Use this when the user asks what to build with no particular market in mind, or wants the strongest current signals' gives a concrete triggering condition tied to user intent. It lacks any negative guidance or a named alternative (e.g., 'for a specific category, use search_gaps'), so it stops one step short of full routing guidance.

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

All DDMarketer tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.