Skip to main content
Glama
Data-Dive-Tools

DataDive MCP

Official
by Data-Dive-Tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Remove Keywords from a Niche's Master Keyword List

remove_niche_keywords
Destructive

Use this to undo add_niche_keywords: take keywords back out of a niche's Master Keyword List (MKL). Only keywords that were added to the MKL can be removed — get_niche_keywords shows each keyword's origin.

Instructions

Use this to undo add_niche_keywords: take keywords back out of a niche's Master Keyword List (MKL). Only keywords that were added to the MKL can be removed — get_niche_keywords shows each keyword's origin. What happens depends on that origin, and the response reports it per keyword: removedManual — added by hand (manual), deleted from the niche; sentBackToOutliers / sentBackToResidue — moved in from those lists (outlier / residue), listed there again with their data kept; notRemovable — found by the dive itself (mkl) or not in the niche, left unchanged. To hide a keyword the dive found, use add_keyword_exclusions instead. Free, and safe to repeat: a keyword already removed comes back under notRemovable. Adding a hand-added keyword back later re-dives the niche and costs Dive tokens if the niche is stale by then. Limited to 2 calls per minute per niche.

Input Schema

NameRequiredDescriptionDefault
nicheIdYesThe niche whose Master Keyword List to remove from. Get one from `list_niches`.
keywordsYesThe keywords to take out, 1–100 per call, at most 255 characters each. They are lower-cased and trimmed, and must be unique after that. Put every keyword in one call: this tool allows only 2 calls per minute per niche.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.17.0

TDQS

A4.6/5.0
Behavior5/5

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

Despite annotations already flagging destructiveHint=true, the description goes far beyond: it enumerates the per-keyword outcomes (removedManual, sentBackToOutliers, sentBackToResidue, notRemovable), notes it is free and idempotent, and warns that re-adding later triggers a re-dive that costs Dive tokens. The rate limit (2 calls/min/niche) is also disclosed. This is rich behavioral context annotations cannot carry.

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 and the inverse-relationship, then organized outcomes, then operational constraints. Dense but well-structured; slightly long, though every clause carries real decision-relevant information.

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 no output schema, the description compensates by explaining the per-keyword response codes the agent will encounter. Covers safety (destructive), idempotency, cost implications, rate limits, and the alternative tool—everything needed to invoke correctly.

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 both parameters are already fully documented in the schema. The description adds the behavioral note about lower-casing/trimming and uniqueness, but this is duplicative of the schema. Baseline 3 is appropriate.

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 and resource (remove keywords from a niche's Master Keyword List) and explicitly frames it as the inverse of add_niche_keywords. This clearly distinguishes it from siblings like add_keyword_exclusions and get_niche_keywords.

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?

Explicitly says to use add_keyword_exclusions instead for hiding dive-found keywords, and warns against trying to remove keywords the dive found. Names the condition (origin) that determines behavior, so an agent knows exactly when this tool applies.

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