AccuRanker MCP Tool Reference

This guide lists the tools available through AccuRanker MCP. You do not call these tools directly. You ask your AI assistant in plain language, and the AI assistant chooses which tool to use.

Rank Tracking Data (AccuRanker)

These tools work with AccuRanker rank tracking data. They can return current values and historical data. The main difference is what each row represents and whether the tool returns a list or one specific item.

list_domains

It returns domains available to the connected user. It can include domain-level history fields across tracked keywords. Use it to compare domains or find a domain ID.

get_domain_history

It returns one domain by ID with selected domain-level history fields across tracked keywords over a date range.

get_domain_kpis

It returns selected domain KPIs for two dates, including the value on the data date and the change from the compare date. In supported AI assistants, the result can be shown as a visual KPI widget.

list_keywords

It returns tracked keywords for one domain. It can include rank history, SERP data, search volume, preferred landing page, AI Overview data, and competitor rankings. Use it to compare keywords or find a keyword ID.

get_keyword_ranks

It returns one keyword by ID with selected keyword-level fields over a date range.

list_landing_pages

It returns history grouped by landing page for one domain. Each row is one landing page.

get_landing_page

It returns one landing page by ID with selected landing-page-level history fields over a date range.

list_tags

It returns history grouped by tag for one domain. Each row is one tag.

AI Visibility Data (AccuLLM)

These tools work with AccuLLM AI visibility data and can return current values and historical data. The main difference is what each row represents and whether the tool returns a list or one specific item. AccuLLM tools require an active AccuLLM plan.

list_brands

It returns brands available to the connected user. It can include brand-level history fields across tracked prompts. Use it to compare brands or find a brand ID.

get_brand_history

It returns one brand by ID with selected brand-level history fields across tracked prompts over a date range.

list_prompts

It returns tracked prompts for one brand. It can include prompt responses, cited sources, brand rankings, sentiment, visibility, and related prompts. Use it to compare prompts or find a prompt ID.

get_prompt

It returns one prompt by ID with selected prompt-level fields over a date range.

Filter URLs

These tools convert between AccuRanker URLs and filter data and can generate links to filtered views in AccuRanker or decode existing URLs to see which filters are applied.

encode_filter_url

It creates an AccuRanker URL from domain IDs, dates, an optional segment, and filters. Use it when you want a shareable link to a filtered keyword view.

decode_filter_url

It reads an AccuRanker URL, path, or encoded filter string and returns the filters it contains.

Knowledge Base

search

It searches AccuRanker's built-in glossary, tool reference, field reference, and filter reference. The AI assistant uses it to answer questions about AccuRanker concepts and metrics using AccuRanker's own definitions.

The knowledge base covers rank, CTR, Share of Voice, traffic value, search volume, search intent, keyword fields, search settings, date comparison, forecasting, notifications, filters, and tool behavior.

Field Selection

Most data tools accept a fields list. Field selection keeps responses smaller and faster because the MCP only returns the data the AI assistant needs. You usually do not need to know the exact field names. Valid field names are exposed through the MCP tool schema and field references, and the AI assistant can look them up with the built-in search tool.

Ask in plain language when possible, for example:

• "include rank history and search volume"
• "include competitor rankings"
• "include prompt responses and cited sources"
• "only return share of voice, traffic value, and keyword counts"

Useful field groups and prefixes include:

• Domains: id, domain, display_name, group., competitors., history., history.ranking_distribution., and history.ranking_movement.
• Domain KPIs: keywords, avg_rank, share_of_voice, traffic_value, ctr, search_volume, ai_share_of_voice, ai_search_volume, keywords_with_ai_overview, keywords_top_3, keywords_top_10, keywords_top_20, keywords_top_50, keywords_top_100, and keywords_unranked.
• Keywords: keyword, tags, dynamic_tags, folders, search_type, search_location, search_engine, search_locale, search_volume, search_volume_local, ai_search_volume, preferred_landing_page, ranks, full_serp, people_also_ask, people_also_search_for, and competitor_ranks.
• Landing pages: path, history, and history.ga4.
• Tags: tag and history.
• Brands: domain, display_name, brand_list, group, competitors, history, history.visibility_movement, and history.ranking_distribution.
• Prompts: prompt, description, tags, country_code, results, results.brands, and results.sources.

Filters and Dates

Most data tools accept filters. This is one of the main strengths of the MCP: the AI assistant can combine filters across rank, rank change, search volume, search intent, tags, folders, landing pages, search engine, location, SERP features, AI Overviews, competitors, and AccuLLM fields such as visibility, sentiment, brand mentions, sources, brands, and prompts.

Filters can be combined with AND and OR logic. A normal list of filters is treated as AND. The AI assistant can also nest OR groups inside that list, so a request such as "commercial-intent keywords with search volume above 1000 where rank is 11-20 or rank dropped by more than 5" can be handled as:

search intent is commercial
AND search volume is above 1000
AND (rank is 11-20 OR rank change is worse than -5)

You do not need to know the filter syntax. The AI assistant can use the built-in search tool to find available filters, comparators, and value formats before it calls a data tool. For the full filter reference, see Using dynamic filters.

Dates are passed as period_from and period_to. For history tools, they define the returned date range. For get_domain_kpis, they define the two dates used to calculate KPI changes.