BrightEdge

Use AI Cube (also known as AI HyperCube) tools for brand mention share, citation share, sentiment, and visibility gap analysis across AI engines (ChatGPT, Perplexity, Google AIO, Google AI Mode). Compare AI citation share across multiple brands for a monthly time window. WHEN TO USE: - Compare citation share for multiple brands (e.g. Brand1 vs Brand2 vs Brand3) over two months - Filter out irrelevant prompt categories (e.g. exclude deal/coupon/sale queries) - Get a ranked list of brands by share_of_citations for a given time period KEY PARAMETERS: - brands: list of brand names to compare (primary brand + competitors) - compare_time_range_start / compare_time_range_end: YYYYMM month range (e.g. 202604, 202605) - filters: optional {field, operator, value} filters to narrow prompt scope - sort_by: share_of_citations (default) | citation_count - sort_order: desc (default) | asc [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use AI Cube (also known as AI HyperCube) tools for brand mention share, citation share, sentiment, and visibility gap analysis across AI engines (ChatGPT, Perplexity, Google AIO, Google AI Mode). Compare AI mention share across multiple brands for a monthly time window. WHEN TO USE: - Compare how often multiple brands are mentioned in AI responses over two months - Get a ranked list of brands by share_of_mentions for a given time period - User asks about "share of mentions", "who is winning", "AI visibility", or "mention percentage" - User asks about AI mention share data availability for a brand or domain (does not require tracked prompts to be configured) KEY PARAMETERS: - brands: list of brand names to compare (primary brand + competitors) - compare_time_range_start / compare_time_range_end: YYYYMM month range (e.g. 202604, 202605) - filters: optional {field, operator, value} filters to narrow prompt scope - sort_by: share_of_mentions (default) | mention_count - sort_order: desc (default) | asc [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use AI Cube (also known as AI HyperCube) tools for brand mention share, citation share, sentiment, and visibility gap analysis across AI engines (ChatGPT, Perplexity, Google AIO, Google AI Mode). Compare AI brand sentiment (positive/neutral/negative) across multiple brands for a monthly time window. WHEN TO USE: - Compare sentiment distribution across multiple competing brands on specific prompts - Identify which prompts drive positive or negative sentiment for a brand vs competitors - Requires an explicit list of brands to compare WHEN NOT TO USE: - To see how your own brand's sentiment is trending week over week → use get_trended_ai_primary_brand_sentiment (no brands list needed, returns aggregate % per time period) KEY PARAMETERS: - brands: list of brand names to compare (primary brand + competitors) - compare_time_range_start / compare_time_range_end: YYYYMM month range (e.g. 202604, 202605) - filters: optional {field, operator, value} filters to narrow prompt scope [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use AI Cube (also known as AI HyperCube) tools for brand mention share, citation share, sentiment, and visibility gap analysis across AI engines (ChatGPT, Perplexity, Google AIO, Google AI Mode). Return the top prompts where your brands (and competitors) are most mentioned in AI responses. WHEN TO USE: - To view the actual AI prompts that are driving my brand's (or competitor's) mentions, ranked by demand - Identify which user queries drive the most AI brand mentions - Prioritize content around high-mention prompts - Understand prompt-level brand visibility in AI engines KEY PARAMETERS: - brands: list of brand names (primary brand and/or competitors) - compare_time_range_start / compare_time_range_end: YYYYMM month range (e.g. 202604, 202605) - filters: optional {field, operator, value} filters to narrow prompt scope - sort_by: be_volume (default) - sort_order: desc (default) | asc [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use AI Cube (also known as AI HyperCube) tools for brand mention share, citation share, sentiment, and visibility gap analysis across AI engines (ChatGPT, Perplexity, Google AIO, Google AI Mode). Identify prompts where competitors are cited in AI responses but your brand is not. WHEN TO USE: - When the user would like to see prompts where a specified competitor is cited, but their brand is not mentioned - Find citation gaps where your domain has zero AI citation share - Discover content and link-building opportunities to capture missed AI citations - Prioritize prompts with the highest competitor citation count and no self-brand citation KEY PARAMETERS: - brands: list of brand names to compare (primary brand + competitors) - compare_time_range_start / compare_time_range_end: YYYYMM month range (e.g. 202604, 202605) - cited_domains: list of domains to filter citations by (e.g. ['xyz.com']) - filters: optional additional {field, operator, value} filters - sort_order: desc (default) | asc [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use AI Cube (also known as AI HyperCube) tools for brand mention share, citation share, sentiment, and visibility gap analysis across AI engines (ChatGPT, Perplexity, Google AIO, Google AI Mode). Identify prompts where competitors are mentioned in AI responses but your brand is not. WHEN TO USE: - When the user would like to see prompts where their competitors are mentioned but they are not - Find gaps where your brand has zero AI mention share - Discover content opportunities to capture missed AI visibility - Prioritize prompts with the highest competitor mention count and no self-brand mention KEY PARAMETERS: - brands: list of brand names to compare (primary brand + competitors) - compare_time_range_start / compare_time_range_end: YYYYMM month range (e.g. 202604, 202605) - filters: optional additional {field, operator, value} filters - sort_order: desc (default) | asc [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use this tool only if the user explicitly requests for 'tracked' in their query. Use AI Brand Presence also know as AI Catalyst (AIB) tools for brand mention and citation data across AI engines (ChatGPT, Perplexity, Google AIO, Google AI Mode). AI Brand Presence citation share (domain-level leaderboard). WHEN TO USE: - Domain-level citation comparison - Citation leaderboard across AI engines - "AIO citation check for [prompt]" — checking citation share for a specific tracked AI prompt WHEN NOT TO USE: - Mentions → use get_ai_tracked_prompt_mentions - Sentiment → use get_ai_tracked_prompt_sentiments - All prompts (no citation filter) → use get_ai_tracked_prompts - AEO recommendations for a specific page or URL → use get_aeo_page_recommendation - Finding which pages need AEO work to convert mentions into citations → use get_aeo_pages_recommendation_summary KEY PARAMETERS: - brand_category: competitor_and_own (default) | competitor | own | all - sort_by: share_of_citations | citations_count | avg_rank | change - llm: chatgpt | perplexity | google_aio | google_ai_mode | all (default) - time_range_start / time_range_end: YYYYWW (e.g. 202614); data is weekly — if the user asks for monthly data, multiply the number of months by 4 to get the equivalent number of weeks [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use this tool only if the user explicitly requests for 'tracked' in their query. Use AI Brand Presence also know as AI Catalyst (AIB) tools for brand mention and citation data across AI engines (ChatGPT, Perplexity, Google AIO, Google AI Mode). Returns prompt group gains/losses data for a single week (mention, citation, sentiment, rank per group). WHEN TO USE: - User asks about prompt group performance, gains, or losses at a specific week - Compare prompt groups by mention/citation/sentiment changes - Filter to specific prompt groups using prompt_group_id_list WHEN NOT TO USE: - Full tracked prompt list (per-prompt, not per-group) → get_ai_tracked_prompts - Aggregated brand mention share leaderboard → get_ai_tracked_prompt_mentions - Citation leaderboard → get_ai_tracked_prompt_citations - Sentiment trend → get_ai_tracked_prompt_sentiments KEY PARAMETERS: - time_value: single YYYYWW week (e.g. 202625); data is weekly - prompt_group_id_list: optional list of prompt group IDs to filter; [] returns all groups - llm: chatgpt | perplexity | google_aio | google_ai_mode | all (default) - pagination_limit: default is 10; do NOT increase unless the user explicitly asks [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use this tool only if the user explicitly requests for 'tracked' in their query. Use AI Brand Presence also know as AI Catalyst (AIB) tools for brand mention and citation data across AI engines (ChatGPT, Perplexity, Google AIO, Google AI Mode). AI Brand Presence mention share (brand-level leaderboard). WHEN TO USE: - Aggregated brand-level mention share leaderboard across all prompts (who ranks highest overall) - User explicitly asks for brand mention share or overall mention ranking WHEN NOT TO USE: - Per-prompt domain vs competitor comparison → use get_ai_tracked_prompts (sort_by=competitor_brand_mention) - Retrieving/listing tracked prompts → use get_ai_tracked_prompts - Citations → use get_ai_tracked_prompt_citations - Sentiment → use get_ai_tracked_prompt_sentiments - Checking data availability when tracked prompts may not be set up → use get_ai_prompt_mentions - AEO recommendations for a specific page or URL → use get_aeo_page_recommendation - Finding which pages need AEO work to convert mentions into citations → use get_aeo_pages_recommendation_summary KEY PARAMETERS: - brand_category: competitor_and_own (default) | competitor | own | all - sort_by: mention_percentage | count_of_mentions | brand_rank | mention_percentage_change - llm: chatgpt | perplexity | google_aio | google_ai_mode | all (default) - time_range_start / time_range_end: YYYYWW (e.g. 202614); data is weekly — if the user asks for monthly data, multiply the number of months by 4 to get the equivalent number of weeks [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use this tool only if the user explicitly requests for 'tracked' in their query. Use AI Brand Presence also know as AI Catalyst (AIB) tools for brand mention and citation data across AI engines (ChatGPT, Perplexity, Google AIO, Google AI Mode). AI Brand Presence sentiment trend (over time). WHEN TO USE: - User asks how brand sentiment is trending WHEN NOT TO USE: - Mentions → use get_ai_tracked_prompt_mentions - Citations → use get_ai_tracked_prompt_citations - Multi-brand sentiment compare → use compare_ai_brand_sentiment_by_brand (AI Cube) KEY PARAMETERS: - llm: chatgpt | perplexity | google_aio | google_ai_mode | all (default) - time_range_start / time_range_end: YYYYWW (e.g. 202614); data is weekly — if the user asks for monthly data, multiply the number of months by 4 to get the equivalent number of weeks [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use this tool only if the user explicitly requests for 'tracked' in their query. Use AI Brand Presence also know as AI Catalyst (AIB) tools for brand mention and citation data across AI engines (ChatGPT, Perplexity, Google AIO, Google AI Mode). Returns all tracked prompts with full per-prompt data (mentions, citations, sentiment, intent, rank, related prompts). No pre-filtering. WHEN TO USE: - Browse/search all tracked prompts - See full prompt data across mentions + citations + sentiment - Compare your domain vs a competitor domain at the per-prompt level (use sort_by=competitor_brand_mention or self_brand_mention) - User asks to retrieve/list tracked prompts, with or without a competitor angle - User doesn’t ask for a specific gap or leaderboard view WHEN NOT TO USE: - Aggregated brand mention share leaderboard (not per-prompt) → get_ai_tracked_prompt_mentions - Citation leaderboard → get_ai_tracked_prompt_citations - Sentiment trend → get_ai_tracked_prompt_sentiments KEY PARAMETERS: - sort_by: competitor_brand_mention | self_brand_mention | self_brand_citation | prompt | intents | self_brand_sentiment - llm: chatgpt | perplexity | google_aio | google_ai_mode | all (default) - time_range_start / time_range_end: YYYYWW (e.g. 202614); data is weekly — if the user asks for monthly data, multiply the number of months by 4 to get the equivalent number of weeks - pagination_limit: default is 10; do NOT increase this unless the user explicitly asks for more results — never call this tool a second time automatically with a higher limit to fetch more [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Returns MCP server info: name, version, environment, supported sources. WHEN TO USE: - User asks about server version, MCP version, environment, or supported sources - Quick health check (no domain/account data) KEY PARAMETER: - current_version (REQUIRED) → always pass 2.21 so server can confirm it’s up to date

Return identity information for the currently authenticated user: userid, login, account id, account name, organization id, the list of all BrightEdge accounts the user has access to, and GSC account configuration (available search engines, cadence, and date ranges). User Intent: who am i, my user info, current user, logged in user, my login info, what account am i on, what is my login, what is my organization, which accounts do i have access to, show my accounts, show my associated accounts, what search engines are configured, what cadence options are available for GSC When to Use: - When the user asks about their own identity, account, or organization. - As a lightweight identity check that reveals which BrightEdge accounts are accessible. - Before other GSC calls to discover valid search_engine_device_id / search_engine_group_id pairs. - When the user asks what search engines or cadence options are configured for their GSC account. When NOT to Use: - Domain or keyword analytics — use the appropriate DCX/GSC/KR/SOV tools. - Server version or environment info — use ``get_brightedge_mcp_server_info``.

Use it for all keyword/domain/url related queries. BrightEdge's datacube is loaded with all the required data. Returns per-keyword rows comparing your domain against up to 4 competitors from BrightEdge DataCube (whole-web index). Use comparison_type to get gap keywords (only competitors rank), shared keywords (both rank), or dominator keywords (competitor outranks you). WHEN TO USE: - "which keywords does my competitor rank for that I don't?" - "show me keywords we both rank for" - "which keywords is competitor outranking me on?" DO NOT USE: - want overlap counts/summary instead of the keyword list → use get_competitor_keyword_summary - single domain keyword list with no competitor → use get_keywords_for_domain_or_url - actual clicks or impressions → use GSC tools KEY PARAMETERS: comparison_type — "only_competitor_ranks", "both_domains_rank", or "competitor_outranks_me" domain — your primary domain (required) competitor_domains — 1–4 competitor domains (required) [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use it for all keyword/domain/url related queries. BrightEdge's datacube is loaded with all the required data. Returns keyword overlap counts between your domain and up to 4 competitors (e.g. "how many keywords do I share with competitor X?"). Covers the full web index — any domain, tracked or not. WHEN TO USE: - "how many keywords do I share with a competitor?" - "give me a competitive keyword coverage summary" - "keyword count comparison across domains" DO NOT USE: - want the actual keyword list, not just counts → use get_competitor_keyword_gap_list - avg rank or page-1/2/3 counts for tracked domains → use get_tracked_domains - share-of-voice / market share score → use SOV tools KEY PARAMETERS: domain — your primary domain (required) competitor_domains — 1–4 competitor domains (required) [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use it for all keyword/domain/url related queries. BrightEdge's datacube is loaded with all the required data. Returns SERP feature presence and opportunities for a domain across the full web index — covers featured snippets, AI Overviews, People Also Ask, and more. Covers any domain, not limited to tracked keywords. WHEN TO USE: - "which keywords trigger a featured snippet / AI Overview / People Also Ask?" - "show me SERP feature opportunities for my domain" - "which SERP features am I winning or losing?" - "which SERP features are unlinked to my pages?" - "where are we appearing in SERP features but not properly linked / missed connection opportunities" → set serp_features_view="unlinked_features", is_branded=False - "which SERP features did we gain or lose / full visibility movement in SERP features" → set serp_features_view="gains_and_losses" - "keywords that gained or lost AI Overview coverage between two periods" → set serp_features_view="gains_and_losses" - "AI Overview keyword opportunities" or "find keywords where AI Overview exists but we're not featured" → set serp_features_view="win_opportunities" DO NOT USE: - user says "my tracked keywords" and wants per-keyword SERP rows → use get_tracked_keyword_serp - user says "my tracked keywords" and wants aggregate SERP feature counts → use get_tracked_keyword_serp_summary - just need keyword rankings without SERP feature data → use get_keywords_for_domain_or_url - actual GSC clicks → use GSC tools - "AIO citation check for [prompt]" where the subject is a tracked AI prompt, not a URL → use get_ai_tracked_prompt_citations KEY PARAMETERS: serp_features_view — "my_rankings" (default), "all_features", "win_opportunities", "unlinked_features", or "gains_and_losses" [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use this tool only when the user explicitly asks for Google Search Console (GSC) data. Returns keyword-level click/impression/CTR/position data from Google Search Console with period comparison. WHEN TO USE: - actual clicks, impressions, CTR, or position per keyword from GSC - keyword groups or keyword counts from GSC - which keywords are driving a specific page (use query_for="keyword_groups") DO NOT USE: - tracked keyword rankings from BrightEdge → use get_tracked_keywords - keyword research / DataCube universe → use get_keywords_for_domain_or_url - keywords driving a page by SOV score → use get_share_of_voice_keyword_vs_page_lookup - for a single aggregate summary (total clicks, impressions, CTR, position across everything) → use get_google_search_console_overview_summary - SERP feature coverage changes between periods (e.g. "keywords that lost AI Overview coverage") → use get_domain_or_url_serp_features KEY PARAMETERS: query_for — "keywords" or "keyword_groups" (keywords driving a specific page) return_counts_only — True for totals only, no rows (only applies when query_for="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.

Use this tool only when the user explicitly asks for Google Search Console (GSC) data. Returns a GSC click/impression/CTR/position summary. Not broken down by keyword or page. KEY PARAMETERS: - query_for="overview_summary" → preset windows (week, month, quarter); no date range needed (default) - query_for="time_range_based_summary" → time-range-based comparison; requires compare_time_range_start and compare_time_range_end WHEN TO USE: - user wants a GSC snapshot without specifying explicit date ranges - user names explicit date windows (e.g. "this month vs last month", "Q1 vs Q2") - headline metrics comparison for any period DO NOT USE: - estimated traffic or revenue → use get_tracked_keyword_estimation_summary - tracked keyword ranking KPI summary → use get_tracked_keywords_summary - keyword or page grids → use get_google_search_console_keyword_performance or get_google_search_console_pages_performance [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use this tool only when the user explicitly asks for Google Search Console (GSC) data. Returns page-level click/impression/CTR/position data from Google Search Console with period comparison. WHEN TO USE: - actual clicks, impressions, CTR, or position per page/URL from GSC - page groups or page counts from GSC DO NOT USE: - which keywords drive a specific page → use get_google_search_console_keyword_performance - page SOV score or competitive visibility → use get_share_of_voice_pages - pages ranking for a keyword by SOV score → use get_share_of_voice_keyword_vs_page_lookup - site directory organic gains/losses → use get_pages_gaining_or_losing_trends KEY PARAMETERS: query_for — "pages" (default), "page_groups". return_counts_only — True for totals only, numeric output with no rows. [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use this tool only when the user explicitly asks for SearchIQ data — page speed, schema markup, related keywords, or keyword ranking factor analysis. Returns aggregated ranking factor analysis across all keywords in a keyword group. Surfaces the dominant on-page and off-page signals driving group-level ranking performance, highlighting common strengths and gaps across the group's keywords — benchmarked against competitors and SERP position averages, with a top-10 metrics overlay. WHEN TO USE: - "what ranking factors affect keywords in my '<group name>' group?" - "analyze ranking signals across a keyword group" - "why are keywords in this group ranking where they are?" - getting a consolidated ranking factor view for a topic cluster DO NOT USE: - ranking factors for a single keyword + URL → use get_keyword_page_ranking_factor - keyword group performance stats (clicks, impressions) → use get_keyword_group_summary - related keywords for a seed keyword → use get_related_keywords - tracked keyword rank history → use get_tracked_keyword_history KEY PARAMETERS: keyword_group — the exact name of the keyword group defined in BrightEdge. [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use this tool only when the user explicitly asks for SearchIQ data — page speed, schema markup, related keywords, or keyword ranking factor analysis. Returns a summary of keyword group performance metrics for a domain. For each keyword group shows: on-page, page-speed, and schema category grades, plus which schema types appear most commonly among top-ranking SERP pages for that group's keywords — giving a topic-cluster view of SEO health and schema gaps. WHEN TO USE: - "show me keyword group performance for my domain" - "which keyword groups are doing well / poorly?" - "keyword group summary for <domain>" - getting a topic-cluster view of ranking performance - "what schemas are competitors using for my keyword groups?" DO NOT USE: - keyword-page mapping summary → use get_keyword_page_summary - ranking factors within a specific keyword group → use get_keyword_group_ranking_factor - individual keyword rankings → use get_tracked_keywords or get_keywords_for_domain_or_url - Google Search Console keyword data → use get_google_search_console_keyword_performance KEY PARAMETERS: domain — the domain to summarize (defaults to the primary account domain). pagination_limit — number of keyword groups to return (default 10). pagination_offset — zero-based offset for pagination (default 0). [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use this tool only when the user explicitly asks for SearchIQ data — page speed, schema markup, related keywords, or keyword ranking factor analysis. Returns the on-page ranking factor analysis for a specific keyword and page URL combination. Breaks down content, structure, and keyword-presence signals (word count, keyword density, keyword in title/headings/URL, SEO score, etc.) that influence how the URL ranks for the keyword — benchmarked against competitors and SERP position averages. WHEN TO USE: - "why does this page rank where it does for this keyword?" - "what ranking factors affect <url> for '<keyword>'?" - "analyze ranking signals for a specific keyword + page pair" - diagnosing rank drops or rank improvement opportunities for a page DO NOT USE: - ranking factors at the keyword group level → use get_keyword_group_ranking_factor - domain-wide keyword performance summary → use get_keyword_page_summary - page speed / Core Web Vitals → use get_page_speed - schema markup analysis → use get_page_schema - related keyword discovery → use get_related_keywords KEY PARAMETERS: keyword — the keyword to analyze ranking factors for. url — the full page URL to evaluate against that keyword. [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use this tool only when the user explicitly asks for SearchIQ data — page speed, schema markup, related keywords, or keyword ranking factor analysis. Returns a ranked list of keyword-page pairs with schema coverage and category scores. For each keyword-page pair in the domain, shows the overall on-page, page-speed, and schema category grades, plus which schema types are present and which competitors are using (gap opportunities). Results are ordered by search volume descending, limited to pages ranking in the top 100. WHEN TO USE: - "show me the keyword-page summary for my domain" - "which pages have schema gaps vs competitors?" - "what's my schema coverage across top keywords?" - reviewing overall keyword-page optimization status DO NOT USE: - keyword group-level summary → use get_keyword_group_summary - keyword rankings from DataCube → use get_keywords_for_domain_or_url - per-keyword ranking factor detail → use get_keyword_page_ranking_factor - page speed Core Web Vitals → use get_page_speed - Google Search Console clicks/impressions → use get_google_search_console_keyword_performance KEY PARAMETERS: domain — the domain to summarize (defaults to the primary account domain). pagination_limit — rows per page (default 10). pagination_offset — zero-based offset for pagination (default 0). [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use it for all keyword/domain/url related queries. BrightEdge's datacube is loaded with all the required data. NOTE: DataCube tool — covers the full web index. For keywords in your BrightEdge tracked list, use get_tracked_keywords instead. Returns keyword rankings and movement data for a domain or URL from BrightEdge DataCube. Covers all keyword types: tracked, non-tracked, branded, non-branded. WHEN TO USE: - "what keywords does my site rank for?" / "keywords ranking for [keyword phrase or URL]" - "show me keywords gaining/losing rank/traffic/volume" → set keyword_change_metric - "top keywords by traffic/volume for this domain or URL" - "which non-branded keywords gained the most rank on our product pages" → set keyword_change_metric="rank", is_branded=False, url=<product page URL> DO NOT USE: - "my tracked keywords" or "my BrightEdge list" → use get_tracked_keywords - actual clicks, impressions, real traffic → use get_google_search_console_keyword_performance - SERP feature presence → use get_domain_or_url_serp_features - page/folder gains or losses → use get_pages_gaining_or_losing_trends KEY PARAMETERS: keyword_change_metric — set to "rank", "traffic", or "volume" to see which keywords moved on that metric between start_date and end_date. Omit for current snapshot rankings. order — "desc" returns the biggest gainers first (default); use "asc" when the user asks for losers, drops, or declines. [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use this tool only when the user explicitly asks for engagement analytics, page analytics, site analytics, or page group analytics data. Returns engagement analytics data broken down by individual page URL. WHEN TO USE: - user asks for page-level traffic, visits, or engagement metrics - user wants to see how individual pages are performing in terms of engagement - user asks about bounce rate, time on page, or page views per URL DO NOT USE: - site-wide aggregate metrics → use get_site_analytics - grouped page section performance → use get_page_group_analytics - Google Search Console click/impression data → use get_google_search_console_pages_performance - keyword ranking data → use get_tracked_keywords or get_keywords_for_domain_or_url - source-level filtering by traffic source (google/bing/etc.) — only available in get_site_analytics [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use this tool only when the user explicitly asks for engagement analytics, page analytics, site analytics, or page group analytics data. Returns engagement analytics aggregated by page group (site sections or URL patterns). WHEN TO USE: - user asks for analytics by site section, directory, or page group - user wants to compare engagement across grouped pages (e.g. /blog/, /product/) - user asks how a particular section of the site is performing for engagement DO NOT USE: - individual page URL breakdown → use get_page_analytics - site-wide totals → use get_site_analytics - page group GSC click/impression data → use get_google_search_console_pages_performance with query_for="page_groups" - share of voice by page group → use get_share_of_voice_pages - source-level filtering by traffic source (google/bing/etc.) — only available in get_site_analytics [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use this tool only when the user explicitly asks for SearchIQ data — page speed, schema markup, related keywords, or keyword ranking factor analysis. Returns structured data and schema markup detected on a given page URL. Surfaces schema types (Article, Product, FAQ, BreadcrumbList, etc.), their presence, completeness, and any validation warnings from BrightEdge's crawl data. WHEN TO USE: - "what schema markup does this page have?" - "does this URL have FAQ schema / Product schema?" - "check structured data on <url>" - auditing pages for schema implementation issues DO NOT USE: - page speed or Core Web Vitals → use get_page_speed - keyword ranking data for a page → use get_keywords_for_domain_or_url with a url filter - on-page SEO recommendations (title, meta, headings) → use get_seo_page_recommendations KEY PARAMETERS: url — full URL including protocol (e.g. 'https://www.example.com/product/123'). keyword — optional keyword to evaluate schema as a ranking factor for. [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use this tool only when the user explicitly asks for SearchIQ data — page speed, schema markup, related keywords, or keyword ranking factor analysis. Returns page speed metrics and Core Web Vitals for a given URL. Fetches performance_score, LCP, INP, FID, CLS, TTI, Speed Index, TBT, total byte weight, and DOM size — benchmarked against competitors and SERP averages. WHEN TO USE: - "how fast is this page?" or "what are the Core Web Vitals for this URL?" - "show me LCP, CLS, FID scores for my page" - "page speed analysis for <url>" - diagnosing technical performance issues on a specific page DO NOT USE: - domain-wide keyword or ranking data → use get_keywords_for_domain_or_url - structured data / schema markup → use get_page_schema - ranking factors for a keyword + page combo → use get_keyword_page_ranking_factor KEY PARAMETERS: url — full URL including protocol (e.g. 'https://www.example.com/page'). keyword — optional keyword to evaluate speed metrics as ranking factors for. [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use it for all keyword/domain/url related queries. BrightEdge's datacube is loaded with all the required data. This tool shows which pages are gaining or losing visibility. It is based on rank-based estimated traffic from BrightEdge DataCube. It does NOT show actual Google clicks. WHEN TO USE: - "which sections of my site are gaining/losing visibility?" - "which folders are declining in rankings?" - "show me page gains or page losses by directory" DO NOT USE: - actual click/impression data per page → use get_google_search_console_pages_performance - per-keyword rank movement rows → use get_keywords_for_domain_or_url with keyword_change_metric="rank" - competitive market-share loss by page → use get_share_of_voice_pages KEY PARAMETERS: trend — "gaining" or "losing"; infer from user prompt ("lost/declining/dropped" → "losing", "gained/growing/improving" → "gaining"). For both trends, make two separate calls. [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use this tool only when the user explicitly asks for SearchIQ data — page speed, schema markup, related keywords, or keyword ranking factor analysis. Returns a list of semantically related keywords for a given seed keyword, with rankings and page context for each related term. WHEN TO USE: - "what keywords are related to 'running shoes'?" - "find related terms / variants for this keyword" - "expand keyword coverage around a topic" - building out keyword groups from a seed keyword DO NOT USE: - tracked keyword rankings → use get_tracked_keywords - keyword research with rank/volume data for a domain → use get_keywords_for_domain_or_url - ranking factors for a specific keyword + URL → use get_keyword_page_ranking_factor - keyword group performance summary → use get_keyword_group_summary KEY PARAMETERS: keyword — the seed keyword to find related terms for (e.g. 'running shoes'). pagination_limit — number of related keywords to return (default 10, max 100). [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

This tool returns BrightEdge SEO recommendations analysis data. Return SEO Recommendations for a specific keyword, including competitor comparison. WHEN TO USE: - "what recommendations do I have for this keyword?" - "how can I improve my ranking for this keyword?" - "show me SEO issues for a specific keyword" - "who are the top 10 ranking pages for this keyword?" - "how does my page compare onpage to competitors for this keyword?" DO NOT USE: - domain-wide keyword summary → use get_seo_keywords_recommendation_summary - page-level recommendations → use get_seo_page_recommendations - keyword rank history → use get_tracked_keyword_history REQUIRED PARAM: - keyword [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

This tool returns BrightEdge SEO recommendations analysis data. Return a paginated list of keywords with their SEO recommendation data. WHEN TO USE: - "show me keyword recommendations across my domain" - "which keywords have the most recommendations?" - "what SEO issues exist at the keyword level?" - "show me keywords sorted by search volume with recommendation counts" DO NOT USE: - single-keyword detail → use get_seo_keyword_recommendations - page-level recommendations → use get_seo_pages_recommendation_summary - keyword rank/traffic data → use get_tracked_keywords or GSC 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.

This tool returns BrightEdge SEO recommendations analysis data. Return SEO Recommendations for a specific page URL. WHEN TO USE: - "what recommendations do I have for this page?" - "how can I improve this URL?" - "show me SEO issues for this page" - "what should I fix on this page?" DO NOT USE: - domain-wide recommendation summary → use get_seo_pages_recommendation_summary - keyword rank data → use get_keywords_for_domain_or_url - page traffic data → use get_google_search_console_pages_performance [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

This tool returns BrightEdge SEO recommendations analysis data. Return an aggregate summary of SEO Recommendations across all pages for a domain. WHEN TO USE: - "give me a recommendations summary for my domain" - "how many recommendations do I have?" - "what are the top issues across my site?" - "show me a breakdown of recommendations by category" - "which pages need the most attention?" DO NOT USE: - single-page recommendations → use get_seo_page_recommendations - keyword/traffic analytics → use DCX or GSC 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.

Use this tool only if the user explicitly requests Share of Voice or SOV data. Returns a summary of Share of Voice (SOV) domains for the current account. WHAT IT DOES: - Summarize tracked domains (your domain + competitors). - Provides summary metrics: SOV score, volume, rank, and time-range comparisons. WHEN TO USE: - To see a summary of all domains in the SOV set. - To analyze tracked competitor domains share of voice results. - To compare a specific competitor domain with the user's domain. - To get a high-level competitive domain summary. DO NOT USE: - For keyword-level SOV → use get_share_of_voice_keywords. - For page-level SOV → use get_share_of_voice_pages. - For keyword gap comparison → use get_competitor_keyword_summary or get_competitor_keyword_gap_list. - For BrightEdge tracked domain rankings → use get_tracked_domains. - For Google Search Console clicks/impressions/CTR → use GSC tools. KEY PARAMETERS: - compare (default "top_domains") → comparison group. - volume_scale (default "brightedge_volume") → scoring scale. - rank_type (default "blended_rank") → ranking type. - keywords_type → include all, branded, or non-branded keywords. - filters → filter by a specific domain. [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use this tool only if the user explicitly requests Share of Voice or SOV data. Pass a keyword to see all pages ranking for it. Pass a page_url to see all keywords that page ranks for. - If you give a keyword, it shows the pages ranking for that keyword with their SOV scores. - If you give a page_url, it shows the keywords that page ranks for with their SOV scores. WHEN TO USE: - Ask "Which pages rank for keyword X?" and provide keyword=... - Ask "What keywords does this page rank for?" and provide page_url=... - To see competitor pages for a keyword, provide keyword=... and filter by domain. - To see keywords where our page is in the top 3, provide page_url=... and filter by rank less than 4. DO NOT USE: - Do not use this tool for actual Google Search Console clicks. Use GSC tools instead. - Do not use this tool for overall keyword or page SOV summaries. Use keyword/page SOV tools instead. KEY PARAMETERS: - keyword → find pages for that keyword. - page_url → find keywords for that page. - compare (default "top_domains") → defines who to compare against. - volume_scale (default "brightedge_volume") → scoring scale for SOV metrics. - rank_type (default "blended_rank") → blended vs classic ranking. - keywords_type → choose whether to include all keywords or only branded/non-branded keywords. NOTE: If both keyword and page_url are given, the keyword takes priority and the page_url is ignored. [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use this tool only if the user explicitly requests Share of Voice or SOV data. This tool shows keyword-level SOV metrics. It measures competitive visibility per keyword. WHEN TO USE: - Ask "Which keywords have the highest SOV score?" to see top keywords. - Ask "Show keywords we gained or lost SOV on vs last week" to compare changes. - Ask "How many keywords are in our SOV universe?" and set count=True. DO NOT USE: - Do not use this tool for actual clicks, impressions, or CTR. Use get_google_search_console_keyword_performance. - Do not use this tool for tracked keyword rankings. Use get_tracked_keywords. - Do not use this tool for untracked keyword research. Use get_keywords_for_domain_or_url. - Do not use this tool for "keywords ranking for [keyword phrase or URL]" — use get_keywords_for_domain_or_url. - Do not use this tool for page-level SOV. Use get_share_of_voice_pages. - Do not use this tool for keyword↔page drill-down. Use get_share_of_voice_keyword_vs_page_lookup. - Do not use this tool for SERP feature presence, unlinked features, missed SERP connection opportunities, SERP feature gains/losses, or SERP visibility movement. Use get_domain_or_url_serp_features. KEY PARAMETERS: - time_range_start / time_range_end → set both to get comparison fields. - domain_to_filter → convenience shorthand for filtering by a single domain. [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use this tool only if the user explicitly requests Share of Voice or SOV data. This tool shows page-level SOV metrics. It measures competitive visibility per landing page. It does NOT show clicks or raw rank. WHEN TO USE: - Ask "Which pages have the highest SOV score?" to see top pages. - Ask "Show pages that gained or lost the most SOV this month vs last month" to compare changes. - Ask "How many unique pages rank in our SOV universe?" and set count=True. - To see competitor pages, filter by domain name. - To see only our own pages, filter by domain_type=1. DO NOT USE: - Do not use this tool for actual page clicks, impressions, or CTR. Use get_google_search_console_pages_performance. - Do not use this tool for site section or directory gains/losses. Use get_pages_gaining_or_losing_trends. - Do not use this tool for estimated visits per page. Use get_tracked_keyword_estimation. - Do not use this tool for keyword-level SOV. Use get_share_of_voice_keywords. - Do not use this tool for keyword↔page drill-down. Use get_share_of_voice_keyword_vs_page_lookup. KEY PARAMETERS: - compare (default "top_domains") → defines which competitors to compare against (own domain + tracked competitors, or just own domain). - volume_scale (default "brightedge_volume") → scoring scale for SOV metrics (Google volume-weighted or BrightEdge volume-weighted). - rank_type (default "blended_rank") → blended vs classic ranking. - keywords_type → choose whether to include all keywords or only branded/non-branded keywords in the SOV calculation. [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use this tool only if the user explicitly requests for 'tracked keyword' not 'keyword'. Current-period rank snapshot or search volume for a single tracked keyword from BrightEdge Keyword Reporting v3. Requires keyword_id or keyword text. Returns one row per search engine (type='rank') or one row with search volume (type='search_volume'). WHEN TO USE: - "what is the rank for [keyword] across search engines?" - "what is the search volume for [keyword]?" - drilling into one specific named tracked keyword DO NOT USE: - rankings for many keywords at once → use get_tracked_keywords - rank history over time for one keyword → use get_tracked_keyword_history - search volume for untracked keywords → use get_keywords_for_domain_or_url KEY PARAMETERS: details_type — 'rank' (default): rank per search engine + page_url; 'search_volume': monthly search volume. keyword_id or keyword — one must be provided. [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.

Use this tool only when the user explicitly asks what BrightEdge autopilot has published or deployed to a page — injected internal links, schema markup, or page copy changes (title, H1, meta description). Detects what BrightEdge has published on a given page URL. Reports three categories of BrightEdge-published content: - related_links: internal links injected on the page - schemas: structured data / schema markup types injected (e.g. Product, FAQ) - page_info: page element updates (title, H1, meta description) WHEN TO USE: - "what has BrightEdge published on this page?" - determine whether BrightEdge has published changes to a URL - verify added schema.org structured data - check for title tag, H1, or meta description updates - identify related / internal / "more like this" links added by BrightEdge - audit BrightEdge-published changes on a specific page DO NOT USE: - checking schema markup from crawl data → use get_page_schema - AI bot/crawler traffic, page visits, or HTTP status by bot → use get_ai_agent_page_visit_* tools KEY PARAMETERS: url — full page URL including protocol (e.g. 'https://www.example.com/page') [IMPORTANT] ALWAYS WARN USERS: If the response contains an actions array, always inform the user using the label value and follow the action instruction.