compare_competitor_domain_gap_keywords
ChatGPTUse it for all keyword/domain analysis, which covers the entire web keyword universe. DATA SOURCE: BrightEdge DataCube (DCX) Performs row-level keyword gap analysis between a primary domain and one or more competitor domains, using the BrightEdge DataCube (DCX). Works for any domain on the web. Returns: One row per keyword, showing the keyword's rank across compared domains, along with volume and top-ranking URL. Key fields: keyword, classic_rank, rank_change, volume, volume_change, top_ranking_url Use when: - User wants a list of specific keywords a competitor ranks for that the primary domain does not - User needs per-keyword competitive gap rows (not aggregates) Do not use when: - Only one domain is provided — requires at least one competitor domain (domains must not be empty or omitted); route to DCX get_keywords_ instead - User wants high-level aggregate summaries (total counts, coverage %) — use KR tools - User wants GSC click/impression data — use GSC tools - User is searching keywords for a single site with no competitor — use DCX get_keywords_ tools [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.
compare_competitor_performance
ChatGPTUse it for all keyword/domain analysis, which covers the entire web keyword universe. DATA SOURCE: BrightEdge DataCube (DCX) Returns an aggregate competitive summary comparing a primary domain against one or more competitor domains — one row per domain, not per keyword. Works for any domain on the web. Returns: One row per domain with high-level keyword coverage and traffic metrics. Key fields: domain, traffic_share, keywords, traffic_estimate, keywords_page1, keywords_page2, keywords_page3, keywords_rank1, keywords_rank2to5 Use when: - User wants a high-level aggregate comparison across domains (totals, coverage percentages) - User asks "how does my domain compare to competitors overall?" or "how many keywords do we share?" - User wants one-row-per-domain competitive snapshot, not a keyword-by-keyword breakdown Do not use when: - User wants a specific list of gap/shared/dominator keyword rows — use compare_competitor_domain_gap_keywords instead (returns per-keyword rows) - Only one domain is provided — requires at least one competitor domain in domains; route to DCX get_keywords_* instead - User wants GSC click/impression data — use GSC tools instead - User wants SOV/share-of-voice market share — use SOV tools instead Hard constraints: - domains must not be empty — this tool requires at least one competitor domain - Returns aggregate counts only; for row-level keyword data use compare_competitor_domain_gap_keywords [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.
get_brightedge_mcp_server_info
ChatGPTReturn metadata about this MCP server instance: name, version, environment, and the list of supported tool categories. The known version of this server is 1.1. `known_version is a required parameter — always pass this value so the server can confirm whether it is up to date. User Intent: server info, server version, mcp version, what version is this, what tools are available, server environment, is this staging or production, what is this server, mcp server details When to Use: - When the user asks about the MCP server version, environment, or tool categories. - As a lightweight health/identity check that requires no domain or account data. When NOT to Use: - GSC account configuration (search engines, cadence, date ranges) — use get_google_search_console_account_details`. - Tool-specific usage or parameter details — consult individual tool docstrings. - Any BrightEdge analytics data (DCX, GSC, KR, SOV) — use the appropriate domain tools.
get_google_search_console_all_keyword_performance
ChatGPTDATA SOURCE: Google Search Console (GSC) — actual click/impression data from Google. User Intent: keyword performance GSC, which keywords lost the most clicks, keyword click drop, top gaining keywords, keyword impressions change, CTR per keyword GSC, average position per keyword, keyword-level GSC data, actual clicks per keyword, actual impressions per keyword, GSC query list, keyword click delta, click decline per keyword, GSC position change per keyword, real traffic per keyword from Google, google search console keyword data Purpose: Keyword-level GSC performance grid with period-over-period comparison. Each row is a keyword with Clicks, Impressions, Average CTR, Average Position, and their changes versus the previous period. Returns all keywords (branded + non-branded combined). When to Use: - Click, impression, CTR, or position data from Google Search Console at keyword level. - Finding top losing or gaining keywords over a period. - Default: use the two most recent available periods. When NOT to Use: - Branded-only keywords — use `get_google_search_console_branded_keyword_performance instead. - Non-branded-only keywords — use get_google_search_console_nonbranded_keyword_performance instead. - Page-level data — use get_google_search_console_page_performance instead. - Tracked keyword rankings from BrightEdge — use get_tracked_keywords instead. - Estimated/modelled traffic per keyword — use get_tracked_keyword_estimation` instead.
get_google_search_console_branded_keyword_performance
ChatGPTDATA SOURCE: Google Search Console (GSC) — actual click/impression data from Google. User Intent: branded keyword performance GSC, branded keywords gaining clicks, branded keyword click change, top branded queries, brand keyword impressions, CTR for branded terms, position change branded keywords, GSC branded keyword clicks, real branded traffic from Google Purpose: Branded keyword-level GSC performance grid with period-over-period comparison. Each row is a branded keyword with Clicks, Impressions, Average CTR, Average Position, and their changes versus the previous period. Branded keywords only. When to Use: - User asks specifically about branded keyword performance or brand terms. - Default: use the two most recent available periods. When NOT to Use: - Non-branded keywords — use `get_google_search_console_nonbranded_keyword_performance instead. - All keywords combined — use get_google_search_console_all_keyword_performance instead. - Page-level data — use get_google_search_console_page_performance instead. - Tracked keyword rankings from BrightEdge — use get_tracked_keywords instead. - Estimated/modelled traffic per keyword — use get_tracked_keyword_estimation` instead.
get_google_search_console_nonbranded_keyword_performance
ChatGPTDATA SOURCE: Google Search Console (GSC) — actual click/impression data from Google. User Intent: non-branded keyword performance GSC, non-branded keywords losing clicks, non-branded keyword click drop, top non-branded queries, non-brand impressions change, CTR for non-branded terms, position change non-branded keywords, non-branded keyword actual clicks, real non-branded traffic from Google, click decline non-branded, GSC position change non-branded keywords Purpose: Non-branded keyword-level GSC performance grid with period-over-period comparison. Each row is a non-branded keyword with Clicks, Impressions, Average CTR, Average Position, and their changes versus the previous period. Non-branded keywords only. When to Use: - User asks specifically about non-branded keyword performance. - Default: use the two most recent available periods. When NOT to Use: - Branded keywords — use `get_google_search_console_branded_keyword_performance instead. - All keywords combined — use get_google_search_console_all_keyword_performance instead. - Page-level data — use get_google_search_console_page_performance instead. - Tracked keyword rankings from BrightEdge — use get_tracked_keywords instead. - Estimated/modelled traffic per keyword — use get_tracked_keyword_estimation` instead.
get_google_search_console_page_performance
ChatGPTDATA SOURCE: Google Search Console (GSC) — actual click/impression data from Google. User Intent: page performance GSC, top pages by impressions, page click change, URL performance google search console, which pages lost impressions, page-level CTR, page position change, landing page GSC data, actual GSC clicks per page URL, landing page actual impressions from Google, top pages losing actual clicks, page click decline actual GSC data, google search console page data, page performance by URL actual clicks not estimated not SOV Purpose: Page-level GSC performance grid with period-over-period comparison. Each row is a page URL with Clicks, Impressions, Average CTR, Average Position, and their changes versus the previous period. KEY SIGNAL: use this tool when the user asks about "clicks", "impressions", "CTR", or "actual traffic" per page. NOT for share of voice or estimated traffic. When to Use: - Actual GSC click/impression/CTR/position data at the page or URL level. - Finding top or bottom pages by clicks, impressions, CTR, or position. - Default: use the two most recent available periods. When NOT to Use: - Page-level SOV score or market share — use `get_share_of_voice_pages instead. Rule of thumb: "share of voice", "SOV", "competitive visibility" → get_share_of_voice_pages; "clicks", "impressions", "CTR", "actual traffic" → this tool. - Keyword-level data — use get_google_search_console_all_keyword_performance, get_google_search_console_branded_keyword_performance, or get_google_search_console_nonbranded_keyword_performance instead. - Estimated traffic per page — use get_tracked_keyword_estimation` instead (GSC is actual clicks, not modelled estimates).
get_google_search_console_performance
ChatGPTDATA SOURCE: Google Search Console (GSC) — actual click/impression data from Google. User Intent: GSC performance summary, google search console comparison, clicks vs previous period, period-over-period GSC, monthly quarterly weekly GSC comparison Purpose: Period-over-period comparison of all key GSC metrics for a user-specified date window: Clicks, Impressions, Average CTR, Average Position, Keyword Count, Page Count. Each metric includes the current value, absolute change, and percentage change. Also includes the current overview (selected period label and headline click change). When to Use: - User names explicit date windows (e.g. "Q1 2026 vs Q4 2025", "this month vs last month"). - Default: use the two most recent available periods (latest period and latest period minus 1). When NOT to Use: - Estimated traffic or revenue — those are modelled, not actual GSC clicks. - Keyword-level data — use `get_google_search_console_all_keyword_performance, get_google_search_console_branded_keyword_performance, or get_google_search_console_nonbranded_keyword_performance instead. - Page/URL-level data — use get_google_search_console_page_performance` instead.
get_keywords_driving_opportunity
ChatGPTUse it for all keyword/domain analysis, which covers the entire web keyword universe. DATA SOURCE: BrightEdge DataCube (DCX) Shows keyword-level rows for a domain filtered by a rank position range (e.g. ranks above 20 or below 3), sourced from the BrightEdge DataCube (DCX). Used to surface untracked keyword opportunities based on where a domain currently ranks. Returns: One row per keyword, including rank, rank change, estimated traffic, and volume. Key fields: keyword, classic_rank, rank_change, estimated_traffic, estimated_traffic_change_int, volume, volume_change Note: time_range is required when both start and end dates are provided; otherwise API defaults apply. Use when: - User wants untracked keywords ranking within a specific position range (e.g. "keywords ranking between positions 5 and 20") - User is looking for quick-win or opportunity keywords based on rank thresholds Do not use when: - User refers to "my tracked keywords" or a named keyword from their BrightEdge list — use DCX get_tracked_keyword* instead - User wants GSC click/impression/CTR data — use GSC tools - User wants SERP feature analysis - User wants a single-keyword SERP competitor breakdown - User wants keyword gap analysis against a competitor — use DCX compare_competitor_domain_gap_keywords [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.
get_keywords_losing_rank
ChatGPTUse it for all keyword/domain analysis, which covers the entire web keyword universe. DATA SOURCE: BrightEdge DataCube (DCX) Shows keyword-level rows for a domain where organic rankings have declined, sourced from the BrightEdge DataCube (DCX). Works for any domain on the web — not limited to BrightEdge-tracked domains. Returns: One row per keyword, including rank, rank change, estimated traffic, and volume. Key fields: keyword, classic_rank, rank_change, estimated_traffic, estimated_traffic_change_int, volume, volume_change Note: time_range is required when both start and end dates are provided; otherwise API defaults apply. Use when: - User wants to find untracked keywords where a domain has lost ranking positions - User asks for organic keyword visibility for any domain (single domain, no competitor mentioned) — this is the default starting tool for single-domain organic keyword lookups (e.g. "top keywords for domain.com", "what does X.com rank for") - The domain is unrecognized or external — DCX works for any domain; do not attempt SOV or KR tools for untracked domains as they will return empty or unauthorized results Do not use when: - User refers to "my tracked keywords" or a named keyword from their BrightEdge list — use DCX get_tracked_keyword_* instead - User asks about "page gains" or page-level views — this tool is keyword-level only, not page or section level - User wants GSC click/impression/CTR data — use GSC tools - User wants SERP feature analysis - User wants a single-keyword SERP competitor breakdown - User wants keyword gap analysis against a competitor — use DCX compare_competitor_domain_gap_keywords Hard constraints: - If the user mentions "my tracked keywords", route to KR tools — this tool only covers the DCX keyword universe - This tool returns keyword-level rows only — never use it for page-level or section-level questions [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.
get_keywords_with_aioverview_opportunity
ChatGPTUse it for all keyword/domain analysis, which covers the entire web keyword universe. DATA SOURCE: BrightEdge DataCube (DCX) Shows keywords where an AI Overview (AIO) SERP feature is present but the domain does not yet have a linked page capturing it — surfacing AIO capture opportunities. Works for any domain. Returns one row per keyword. Returns: One row per keyword with an AI Overview opportunity. Key fields: keyword, classic_rank, volume (ordered descending) Use when: - User wants to find keywords where an AI Overview appears and the domain has an opportunity to be featured - User asks about "AI overview opportunity", "AIO opportunity", "keywords with AI overview", or "AI overview gaps" - User wants to discover which keywords trigger AI Overviews that the domain could target Do not use when: - User wants all SERP features (not just AI Overview) - User wants GSC click/impression data — use GSC tools instead - User refers to "my tracked keywords" — use KR get_tracked_keyword* instead Hard constraints: - This tool is scoped to AI Overview (type=42) only — for other SERP features use get_keyword_serp_features - Results are keyword-level rows, not page or section level [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.
get_pages_gaining_rank
ChatGPTUse it for all keyword/domain analysis, which covers the entire web keyword universe. DATA SOURCE: BrightEdge DataCube (DCX) Shows site sections (URL directories/folders) where organic visibility has improved, sourced from BrightEdge DataCube (DCX). Works for any domain. Returns one row per URL directory/path prefix, not per keyword. Returns: One row per site section/directory gaining organic visibility. Key fields: directory, previous_estimated_traffic, estimated_traffic, estimated_traffic_change_int (ordered ascending) Use when: - User wants to see which site sections or URL directories are gaining organic visibility - User asks about "page gains", "pages gaining", "directory gains", "section gains", or "which folders are growing" - User wants a section-level (not keyword-level) view of organic visibility gains Do not use when: - User wants keyword-level organic gains — use get_keywords_search_results with metric="rank" instead (returns per-keyword rows) - User wants GSC click/impression data per page — use GSC tools instead - User wants page-level competitive market share gains — use get_share_of_voice_pages instead Hard constraints: - This tool returns section/directory-level rows only — never use it for per-keyword questions - Results are rank-based organic visibility, not actual click data [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.
get_pages_losing_rank
ChatGPTUse it for all keyword/domain analysis, which covers the entire web keyword universe. DATA SOURCE: BrightEdge DataCube (DCX) Shows site sections (URL directories/folders) where organic visibility has declined, sourced from BrightEdge DataCube (DCX). Works for any domain. Returns one row per URL directory/path prefix, not per keyword. Returns: One row per site section/directory losing organic visibility. Key fields: directory, previous_estimated_traffic, estimated_traffic, estimated_traffic_change_int (ordered descending) Use when: - User wants to see which site sections or URL directories are losing organic visibility - User asks about "page losses", "pages losing", "directory losses", "section losses", or "which folders are declining" - User wants a section-level (not keyword-level) view of organic visibility losses Do not use when: - User wants keyword-level organic losses — use get_keywords_losing_rank instead (returns per-keyword rows) - User wants GSC click/impression data per page — use GSC tools instead - User wants page-level competitive market share losses — use get_share_of_voice_pages instead Hard constraints: - This tool returns section/directory-level rows only — never use it for per-keyword questions - Results are rank-based organic visibility, not actual click data [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.
get_share_of_voice_competitive_domains
ChatGPTDATA SOURCE: Share of Voice (SOV) — competitive visibility scoring universe. User Intent: List domains in SOV universe, which domains are tracked in SOV, SOV competitor domain list, domains in competitive set, SOV domain universe, list all tracked competitors, what domains are in our SOV universe. Purpose: Returns the list of domain names in the account's SOV universe — own domain plus tracked competitor domains. Universe listing only, not a ranked SOV metrics view. When to Use: - "Which domains are in our SOV competitive set?" - "List all tracked competitor domains." When NOT to Use: - Multi-domain keyword gap analysis → use DCX compare tools instead - Keyword-level SOV → use `get_share_of_voice_keywords instead - Page-level SOV → use get_share_of_voice_pages` instead Key fields: domain_name
get_share_of_voice_keywords
ChatGPTDATA SOURCE: Share of Voice (SOV) — competitive SOV score and market share per keyword. User Intent: Keyword-level SOV scores, rankings, gains/losses, and competitive visibility. Covers branded, non-branded, and competitor keyword SOV comparisons. Purpose: Returns one row per keyword with SOV score, volume, rank, and optional period-over-period diffs when compare_time_range is provided. When to Use: - Highest SOV keywords, SOV gains/losses vs prior period When NOT to Use: - Clicks/impressions/CTR → Google Search Console keyword tools - Tracked keyword rankings → Tracked Keyword tools Key fields: keyword, rank, sov_score, sov_volume, sov_score_diff, page_url, domain
get_share_of_voice_pages
ChatGPTDATA SOURCE: Share of Voice (SOV) — competitive SOV score and market share per page. NOT clicks or rank. User Intent: Page-level SOV scores, rankings, gains/losses, and competitive visibility. Covers own pages, competitor pages, and keyword-group scoping. Purpose: Returns one row per landing page with SOV score, volume, rank, total ranking keywords, and optional period-over-period diffs when compare_time_range is provided. When to Use: - Highest SOV pages, SOV gains/losses vs prior period When NOT to Use: - Actual page clicks/impressions/CTR → Google Search Console page tools - Site section/directory organic gains by rank → DataCube directory tools - Modelled estimated visits per page → Tracked Keywords estimation tools Key fields: page_url, rank, sov_score, sov_volume, total_keywords, sov_score_diff, domain
get_tracked_keyword_blended_rank
ChatGPTOnly use this tool if the user explicitly requests tracked keyword ranking. DATA SOURCE: BrightEdge Keyword Reporting (KR) Returns row-level ranking data for keywords explicitly added to the user's BrightEdge tracked keyword list. Requires the domain to be actively tracked in the BrightEdge account. Returns: One row per keyword showing current and previous blended rank, rank change, ranking URL, and search volume. Key fields: keyword, search_volume, blended_rank, blended_rank_diff, page_num, page_url Note: Domain is auto-resolved from the authenticated account. Read-only. Use when: - User explicitly mentions "my tracked keywords", "my BrightEdge keywords", or "my keyword list" - User wants to browse, filter, or drill into their BrightEdge tracked keyword set - User wants rank movements (gains, losses, page 1 movers, dropped from page 1) within their tracked list - User wants keyword group rollups or group-level rank data from their tracked groups - Default choice for any tracked-keyword rank query — prefer this over classic rank unless the user explicitly says "classic rank" or "organic rank" Do not use when: - User does not say "my tracked keywords" — default to DCX tools instead - Domain is not confirmed as tracked in BrightEdge — this tool requires active tracking and will return empty results otherwise - User wants keywords beyond their tracked list — use DCX get_keywords* tools (full DCX universe) - User explicitly requests "classic rank" or "organic rank" — use get_tracked_keyword_classic_rank instead - User wants GSC click/impression/CTR data — use GSC tools - User wants SOV score or market share — use SOV tools Hard constraint: - The word "tracked" in the user's query is the primary signal to use this tool. Without it, default to DCX tools. - This tool strictly covers the BrightEdge tracked keyword list — never the broader DCX keyword universe. - This is the DEFAULT rank tool for tracked keywords. Use classic rank only when the user explicitly asks for it. [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.
get_tracked_keyword_brightedge_volume
ChatGPTOnly use this tool if the user explicitly requests tracked keyword ranking. DATA SOURCE: BrightEdge Keyword Reporting (KR) Returns row-level search volume data for keywords explicitly added to the user's BrightEdge tracked keyword list, alongside blended ranking signals. Requires the domain to be actively tracked in the BrightEdge account. Returns: One row per keyword showing search volume, current and previous blended rank, rank change, and ranking URL. Key fields: keyword, search_volume, blended_rank, blended_rank_diff, page_num, page_url Note: Domain is auto-resolved from the authenticated account. Read-only. Use when: - User explicitly mentions "my tracked keywords" and wants search volume data for their tracked list - User wants to sort, filter, or analyze their tracked keywords by search volume - User wants volume alongside blended rank for their BrightEdge tracked keyword set Do not use when: - User does not say "my tracked keywords" — default to DCX tools instead - Domain is not confirmed as tracked in BrightEdge — this tool requires active tracking and will return empty results otherwise - User wants keywords beyond their tracked list — use DCX get_keywords* tools (full DCX universe) - User wants GSC click/impression/CTR data — use GSC tools - User wants SOV score or market share — use SOV tools Hard constraint: - The word "tracked" in the user's query is the primary signal to use this tool. Without it, default to DCX tools. - This tool strictly covers the BrightEdge tracked keyword list — never the broader DCX keyword universe. [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.
get_tracked_keyword_classic_rank
ChatGPTOnly use this tool if the user explicitly requests tracked keyword ranking. DATA SOURCE: BrightEdge Keyword Reporting (KR) Returns row-level classic ranking data for keywords explicitly added to the user's BrightEdge tracked keyword list. Requires the domain to be actively tracked in the BrightEdge account. Returns: One row per keyword showing current and previous classic rank, rank change, ranking URL, and search volume. Key fields: keyword, search_volume, rank, rank_diff, page_num, page_url Note: Domain is auto-resolved from the authenticated account. Read-only. Use when: - User explicitly mentions "my tracked keywords" AND explicitly says "classic rank" or "organic rank" - User wants to browse, filter, or drill into their BrightEdge tracked keyword set specifically by classic (organic-only) rank - User wants classic rank movements within their tracked list and the word "classic" or "organic" appears in the query - User wants keyword group rollups or group-level classic rank data from their tracked groups Do not use when: - User does not say "my tracked keywords" — default to DCX tools instead - User does not explicitly say "classic rank" or "organic rank" — use get_tracked_keyword_blended_rank instead (blended is the default) - Domain is not confirmed as tracked in BrightEdge — this tool requires active tracking and will return empty results otherwise - User wants keywords beyond their tracked list — use DCX get_keywords* tools (full DCX universe) - User wants blended rank data — use get_tracked_keyword_blended_rank instead - User wants GSC click/impression/CTR data — use GSC tools - User wants SOV score or market share — use SOV tools Hard constraint: - The word "tracked" in the user's query is the primary signal to use this tool. Without it, default to DCX tools. - This tool strictly covers the BrightEdge tracked keyword list — never the broader DCX keyword universe. - Do NOT use this tool unless the user explicitly says "classic rank" or "organic rank". For all generic rank queries, use get_tracked_keyword_blended_rank. [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.
get_tracked_keyword_competitive_comparison_details
ChatGPTOnly use this tool if the user explicitly requests tracked keyword ranking. DATA SOURCE: BrightEdge Keyword Reporting (KR) Returns row-level ranking data for keywords explicitly added to the user's BrightEdge tracked keyword list, sorted by search volume for competitive comparison. Requires the domain to be actively tracked in the BrightEdge account. Returns: One row per keyword showing search volume alongside blended rank, rank change, and ranking URL. Key fields: keyword, search_volume (ordered descending) Note: Domain is auto-resolved from the authenticated account. Read-only. Use when: - User explicitly mentions "my tracked keywords", "my BrightEdge keywords", or "my keyword list" and wants to compare competitive keyword performance - User wants to see their tracked keywords ranked by search volume for competitive prioritization - User wants to identify high-volume tracked keywords and their current ranking position Do not use when: - User does not say "my tracked keywords" — default to DCX tools instead - Domain is not confirmed as tracked in BrightEdge — this tool requires active tracking and will return empty results otherwise - User wants keywords beyond their tracked list — use DCX get_keywords* tools (full DCX universe) - User wants GSC click/impression/CTR data — use GSC tools - User wants SOV score or market share — use SOV tools Hard constraint: - The word "tracked" in the user's query is the primary signal to use this tool. Without it, default to DCX tools. - This tool strictly covers the BrightEdge tracked keyword list — never the broader DCX keyword universe. [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.
get_tracked_keyword_serp_features
ChatGPTOnly use this tool if the user explicitly requests tracked keyword ranking. DATA SOURCE: BrightEdge Keyword Reporting (KR) — tracked keywords only (BrightEdge-managed list). Returns an aggregate count of tracked keywords with presence in each SERP feature category (Google AI Overview, Images, People Also Ask, Videos, etc.) for the selected period. Returns: One row with columns — Period, Keywords with SERP Presence, Keywords with Google AI Overview, Keywords with Images, Keywords with People Also Ask, Keywords with Videos, and % change for each. Key fields: universal_all_space_p1_space, universal_aioverview_self_p1_self, universal_image_self_p1_self, universal_paa_self_p1_self, universal_video_self_p1_self, and their _diff_percent counterparts. Note: Domain and search engine are auto-resolved from the authenticated account. Read-only. Use when: - User asks about SERP feature presence or breakdown for their tracked keywords - User asks about AI Overview, Featured Snippets, PAA, Images, or Videos presence count - User wants a breakdown of which SERP categories their tracked keywords appear in - User wants to compare SERP feature presence period-over-period for tracked keywords Do not use when: - User does not say "my tracked keywords" — default to DCX tools instead - User wants per-keyword SERP feature rows (not aggregate) — use `get_tracked_keyword_serp_features_details - User wants GSC click/impression/CTR data — use GSC tools - User wants SOV score or market share — use SOV tools - User wants standard ranking KPIs (avg rank, page counts) — use get_tracked_keyword_blended_rank or get_tracked_keyword_classic_rank - User wants SERP features for the broad web keyword universe (not tracked list) — use get_keyword_serp_features` Hard constraint: - The word "tracked" in the user's query is the primary signal to use this tool. Without it, default to DCX tools. - This tool strictly covers the BrightEdge tracked keyword list — never the broader DCX keyword universe. [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.
get_tracked_keyword_serp_features_details
ChatGPTOnly use this tool if the user explicitly requests tracked keyword ranking. DATA SOURCE: BrightEdge Keyword Reporting (KR) — tracked keywords only (BrightEdge-managed list). Returns a per-keyword list of tracked keywords that have presence in the specified SERP feature, along with their blended rank, ranking URL, and search volume. Returns: One row per keyword — Keyword, Blended Rank (latest period), Page URL, Search Volume, SERP Feature. Key fields: keyword, blended_rank, page_url, search_volume, category. Note: Domain and search engine are auto-resolved from the authenticated account. Read-only. serp_feature (required) — one of: 'all', 'images', 'videos', 'places', 'carousel', 'news', 'blogs', 'knowledge', 'cafe', 'local_3pack', 'quick_answers', 'apps', 'others', 'top_stories', 'google_jobs', 'people_also_ask', 'knowledge_panel', 'tweets', 'recipes', 'product_shopping_ads', 'text_ads', 'products', 'ai_overviews'. Use when: - User asks for a list of keywords ranking in a specific SERP feature (e.g. People Also Ask, AI Overview) - User wants to see which tracked keywords appear in a particular category with their rank and page URL - User wants per-keyword SERP feature rows for their BrightEdge tracked list Do not use when: - User does not say "my tracked keywords" — default to DCX tools instead - User wants an aggregate count of keywords per SERP feature (not a list) — use `get_tracked_keyword_serp_features - User wants GSC click/impression/CTR data — use GSC tools - User wants SOV score or market share — use SOV tools - User wants standard ranking KPIs without SERP feature filter — use get_tracked_keyword_blended_rank - User wants SERP features for the broad web keyword universe (not tracked list) — use get_keyword_serp_features` Hard constraint: - The word "tracked" in the user's query is the primary signal to use this tool. Without it, default to DCX tools. - This tool strictly covers the BrightEdge tracked keyword list — never the broader DCX keyword universe. [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.
