search_gaps
Search validated software opportunities by keyword. Each gap is a real, recurring user complaint scored for commercial intent (willingness to pay). Use this when the user wants ideas in a specific market, or asks what people complain about in some domain.
This record as markdown: /tools/ddmarketer-mcp/search-gaps.md
What search_gaps does on Ddmarketer
AI agents call search_gaps to retrieve information from Ddmarketer without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Max gaps to return (1-25, default 10). |
query | string | Yes | Keywords describing the market or problem space, e.g. 'shopify accounting' or 'developer onboarding'. |
category | string | — | Optional exact category filter, e.g. 'E-commerce', 'DevTools'. |
Parameters from the server's own tool schema.
Why search_gaps is rated Low
Even though search_gaps only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs search_gaps safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ddmarketer, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_gaps, this is the rule to start with:
search_gaps is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ddmarketer, apply this rule, and every search_gaps call is checked against it from then on.
Questions about search_gaps
Search validated software opportunities by keyword. Each gap is a real, recurring user complaint scored for commercial intent (willingness to pay). Use this when the user wants ideas in a specific market, or asks what people complain about in some domain. It is categorised as a Read tool in the Ddmarketer MCP Server, which means it retrieves data without modifying state.
search_gaps accepts 3 parameters: limit, query, category. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Ddmarketer MCP server in PolicyLayer and add a rule for search_gaps: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Ddmarketer. Nothing to install.
search_gaps is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the search_gaps rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for search_gaps. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
search_gaps is provided by the Ddmarketer MCP server (https://www.ddmarketer.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ddmarketer, and thousands of servers like it.
This server
Across the catalogue