Skip to main content
Glama
Data-Dive-Tools

DataDive MCP

Official
by Data-Dive-Tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Exclude Keywords from a Niche

add_keyword_exclusions
Destructive

Use this to hide irrelevant keywords from a niche's Master Keyword List — e.g. other brands, wrong product types. exact entries hide the one keyword that matches exactly; phrase entries hide every keyword containing the phrase, so…

Instructions

Use this to hide irrelevant keywords from a niche's Master Keyword List — e.g. other brands, wrong product types. exact entries hide the one keyword that matches exactly; phrase entries hide every keyword containing the phrase, so prefer exact unless the user wants a whole family of keywords gone. The excluded keywords drop out of get_niche_keywords at once, wherever they come from: the dive, Outliers, Residue, or ones added with add_niche_keywords. Nothing is deleted: remove_keyword_exclusions brings them back. Only the exclusions change — every other niche setting is kept. Send 1–100 entries in total across exact and phrase; a niche can hold at most 1000 exclusions. Free, no tokens, and safe to repeat: entries already excluded come back under unchanged. Returns added, unchanged and the full exact / phrase lists after the change. Limited to 30 calls per minute per niche, so batch entries into one call.

Input Schema

NameRequiredDescriptionDefault
exactNoExact-match entries to exclude: each one hides the single keyword that matches it exactly. At most 255 characters each; lower-cased and trimmed, and must be unique after that.
phraseNoPhrase-match entries to exclude: each one hides every keyword that contains the phrase (e.g. "puppy" hides "puppy hat" and "hat for puppy"). At most 255 characters each; lower-cased and trimmed, and must be unique after that.
nicheIdYesThe niche whose keyword exclusions to change. Get one from `list_niches`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A4.8/5.0
Behavior5/5

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

Adds rich context beyond annotations: effects propagate to get_niche_keywords across all sources, nothing is deleted and the action is reversible via remove_keyword_exclusions, only exclusions change (other settings kept), idempotent behavior (repeat entries return under `unchanged`), cost (free, no tokens), and a 30 calls/min per-niche rate limit with batching advice. Note a mild tension with destructiveHint=true, since the text stresses the operation is non-destructive and reversible.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then semantics, reversibility, limits, and return values in a logical order. It is dense and fairly long (five-plus clauses), but nearly every clause carries operational value with little waste.

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 mutation tool with no output schema, the description covers reversibility, side effects, batch/size limits, rate limits, cost, and return shape, so an agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/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 `exact`/`phrase`/`nicheId`; baseline is 3. The description adds value by clarifying the semantics of each mode and the decision rule between them ('prefer exact unless', whole-family behavior), pushing it above baseline.

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 (hide/add exclusions) and resource (a niche's Master Keyword List), with concrete examples of what gets excluded (other brands, wrong product types). It is clearly distinguishable from siblings like add_niche_keywords and remove_keyword_exclusions.

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

Usage Guidelines5/5

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

Gives explicit when-to-use (hiding irrelevant keywords from a niche) plus a preference rule for `exact` vs `phrase` ('prefer exact unless the user wants a whole family gone'). It also names the inverse tool, remove_keyword_exclusions, for undoing.

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