io.github.abhibavishi/rankparse-mcp

Est-ce que io.github.abhibavishi/rankparse-mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.abhibavishi/rankparse-mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 80 outils

• batch_lookup≈ 113 tokens

  Get backlinks for up to 50 domains at once

  Paramètres, retour & exemple (1)

  Paramètres

  • domains · array · requis

  Exemple d'appel

  {"name": "batch_lookup", "arguments": {"domains": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• check_credits≈ 82 tokens

  Check remaining credit balance

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "check_credits", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• complete_agent_task≈ 163 tokens

  Mark a queued task done with a plain-text summary (max 2000 characters) of what you found and what you did. The user sees it in RankParse.

  Paramètres, retour & exemple (2)

  Paramètres

  • summary · string · requis
  • task_id · string · requis

  Exemple d'appel

  {"name": "complete_agent_task", "arguments": {"summary": "texte", "task_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_agent_tasks≈ 162 tokens

  Get tasks the user queued for you in RankParse. At the start of any RankParse session, call get_agent_tasks to see work the user queued for you. Work on a task, then call complete_agent_task with a short plain-text summary.

  Paramètres, retour & exemple (2)

  Paramètres

  • status · string · optionnel · open | claimed | all
  • site_id · string · optionnel

  Exemple d'appel

  {"name": "get_agent_tasks", "arguments": {"status": "open", "site_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_anchor_text≈ 115 tokens

  Get anchor text distribution for a domain

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · number · optionnel
  • domain · string · requis

  Exemple d'appel

  {"name": "get_anchor_text", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_backlinks≈ 189 tokens

  Get backlinks for a domain. Default sort=importance returns aggregated referrer rows; sort=recent returns URL-level freshest links. Optional filters: from_domain, link_type, score.

  Paramètres, retour & exemple (6)

  Paramètres

  • sort · string · optionnel · importance | recent
  • limit · number · optionnel
  • score · boolean · optionnel
  • domain · string · requis
  • link_type · string · optionnel
  • from_domain · string · optionnel

  Exemple d'appel

  {"name": "get_backlinks", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_competitor_gap≈ 197 tokens

  Find domains linking to a competitor but not to you: ranked link-building prospects. Under time budget the response may come back with partial=true and scored=false, meaning the results are the raw gap set without domain-authority ranking; retrying the same request usually returns a fully scored answer.

  Paramètres, retour & exemple (3)

  Paramètres

  • vs · string · requis
  • limit · number · optionnel
  • domain · string · requis

  Exemple d'appel

  {"name": "get_competitor_gap", "arguments": {"vs": "texte", "domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_crawl_history≈ 122 tokens

  Get first/last seen dates and total snapshot count for a domain (source: Wayback Machine)

  Paramètres, retour & exemple (1)

  Paramètres

  • domain · string · requis

  Exemple d'appel

  {"name": "get_crawl_history", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_domain_authority≈ 164 tokens

  Get authority score for a domain. If the response has partial=true the lookup timed out or was incomplete: a null score means the authority is unknown (not zero) and the credit was refunded, so retry rather than treating the domain as having no authority.

  Paramètres, retour & exemple (1)

  Paramètres

  • domain · string · requis

  Exemple d'appel

  {"name": "get_domain_authority", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_domain_overlap≈ 131 tokens

  Find domains linking to all queried domains

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · number · optionnel
  • domains · array · requis

  Exemple d'appel

  {"name": "get_domain_overlap", "arguments": {"domains": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_domain_rank≈ 110 tokens

  Get inbound edge count and linking domain stats

  Paramètres, retour & exemple (1)

  Paramètres

  • domain · string · requis

  Exemple d'appel

  {"name": "get_domain_rank", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_google_ads_accounts≈ 185 tokens

  List the Google Ads accounts the connected Google user can access, as 10-digit customer IDs. Use this to help a user pick which account to select when they have more than one. Requires Google Ads to be connected and an Ads account selected. Direct the user to rankparse.com/dashboard/integrations. Returns search volume and competition data, NOT keyword rankings; use the Google Search Console tools for ranking and position data.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_google_ads_accounts", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_google_ads_keyword_ideas≈ 466 tokens

  Discover NEW keyword ideas from seed terms and/or a URL, with average monthly search volume, competition level, and top-of-page bid ranges. Use this for keyword research and content planning: "what should I target?". Supply seed keywords, a URL, or both. Requires Google Ads to be connected and an Ads account selected. Direct the user to rankparse.com/dashboard/integrations. Returns search volume and competition data, NOT keyword rankings; use the Google Search Console tools for ranking and position data.

  Paramètres, retour & exemple (7)

  Paramètres

  • url · string · optionnel
    A page or site URL to derive keyword ideas from, e.g. "https://example.com/pricing"
  • limit · number · optionnel
    Max ideas to return (default Google decides, max 1000)
  • keywords · array · optionnel
    Seed keywords to expand from, e.g. ["seo tools", "backlink checker"]. Max 20; provide these and/or url.
  • language · string · optionnel
    Language resource name, default "languageConstants/1000" (English)
  • geo_target_constants · array · optionnel
    Location resource names, default ["geoTargetConstants/2840"] (United States). Max 10.
  • keyword_plan_network · string · optionnel · GOOGLE_SEARCH | GOOGLE_SEARCH_AND_PARTNERS
    Search network to estimate against (default GOOGLE_SEARCH)
  • include_adult_keywords · boolean · optionnel
    Include adult keywords in results (default false)

  Exemple d'appel

  {"name": "get_google_ads_keyword_ideas", "arguments": {"url": "texte", "limit": 1, "keywords": [], "language": "texte", "geo_target_constants": [], "keyword_plan_network": "GOOGLE_SEARCH"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_google_ads_keyword_metrics≈ 416 tokens

  Get average monthly search volume, competition level, and top-of-page bid ranges for a SPECIFIC list of keywords, with no expansion into related terms. Use this when the user already has keywords in mind and wants them sized: "how much traffic are these worth?". For discovering new keywords instead, use get_google_ads_keyword_ideas. Requires Google Ads to be connected and an Ads account selected. Direct the user to rankparse.com/dashboard/integrations. Returns search volume and competition data, NOT keyword rankings; use the Google Search Console tools for ranking and position data.

  Paramètres, retour & exemple (4)

  Paramètres

  • keywords · array · requis
    The exact keywords to look up, e.g. ["seo api", "rank tracker"]. Max 200 per call; extras are dropped and reported via the "truncated" flag.
  • language · string · optionnel
    Language resource name, default "languageConstants/1000" (English)
  • geo_target_constants · array · optionnel
    Location resource names, default ["geoTargetConstants/2840"] (United States). Max 10.
  • keyword_plan_network · string · optionnel · GOOGLE_SEARCH | GOOGLE_SEARCH_AND_PARTNERS
    Search network to estimate against (default GOOGLE_SEARCH)

  Exemple d'appel

  {"name": "get_google_ads_keyword_metrics", "arguments": {"keywords": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_gsc_country_breakdown≈ 264 tokens

  Get search traffic broken down by country. Useful for understanding geographic audience and international SEO performance. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it. When several Google accounts are connected, the property is read through the account that can see it.

  Paramètres, retour & exemple (4)

  Paramètres

  • site · string · requis
    Property URL e.g. "https://example.com"
  • endDate · string · requis
    End date YYYY-MM-DD
  • rowLimit · number · optionnel
    Max rows (default 25, max 1000)
  • startDate · string · requis
    Start date YYYY-MM-DD

  Exemple d'appel

  {"name": "get_gsc_country_breakdown", "arguments": {"site": "texte", "endDate": "texte", "startDate": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_gsc_date_trends≈ 253 tokens

  Get daily search performance trends (clicks, impressions, CTR, position) over a date range. Useful for spotting ranking changes, traffic drops, or algorithm update impact. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it. When several Google accounts are connected, the property is read through the account that can see it.

  Paramètres, retour & exemple (3)

  Paramètres

  • site · string · requis
    Property URL e.g. "https://example.com"
  • endDate · string · requis
    End date YYYY-MM-DD
  • startDate · string · requis
    Start date YYYY-MM-DD

  Exemple d'appel

  {"name": "get_gsc_date_trends", "arguments": {"site": "texte", "endDate": "texte", "startDate": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_gsc_device_breakdown≈ 231 tokens

  Get search traffic broken down by device type (desktop, mobile, tablet). Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it. When several Google accounts are connected, the property is read through the account that can see it.

  Paramètres, retour & exemple (3)

  Paramètres

  • site · string · requis
    Property URL e.g. "https://example.com"
  • endDate · string · requis
    End date YYYY-MM-DD
  • startDate · string · requis
    Start date YYYY-MM-DD

  Exemple d'appel

  {"name": "get_gsc_device_breakdown", "arguments": {"site": "texte", "endDate": "texte", "startDate": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_gsc_low_ctr_pages≈ 335 tokens

  Find pages with high impressions but low CTR: pages that Google is showing frequently but users aren't clicking. Good starting point for title/description rewrites. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it. When several Google accounts are connected, the property is read through the account that can see it.

  Paramètres, retour & exemple (6)

  Paramètres

  • site · string · requis
    Property URL e.g. "https://example.com"
  • maxCtr · number · optionnel
    Only include pages with CTR at or below this value 0–1 (default 0.05 = 5%)
  • endDate · string · requis
    End date YYYY-MM-DD
  • rowLimit · number · optionnel
    Max rows (default 25, max 1000)
  • startDate · string · requis
    Start date YYYY-MM-DD
  • minImpressions · number · optionnel
    Only include pages with at least this many impressions (default 500)

  Exemple d'appel

  {"name": "get_gsc_low_ctr_pages", "arguments": {"site": "texte", "endDate": "texte", "startDate": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_gsc_low_ctr_queries≈ 354 tokens

  Find search queries with high impressions but low CTR. These are ranking but not getting clicked, usually because the title or meta description is weak or misleading. Fixing these is typically higher ROI than chasing new rankings. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it. When several Google accounts are connected, the property is read through the account that can see it.

  Paramètres, retour & exemple (6)

  Paramètres

  • site · string · requis
    Property URL e.g. "https://example.com"
  • maxCtr · number · optionnel
    Only include queries with CTR at or below this value 0–1 (default 0.05 = 5%)
  • endDate · string · requis
    End date YYYY-MM-DD
  • rowLimit · number · optionnel
    Max rows (default 50, max 1000)
  • startDate · string · requis
    Start date YYYY-MM-DD
  • minImpressions · number · optionnel
    Only include queries with at least this many impressions (default 100)

  Exemple d'appel

  {"name": "get_gsc_low_ctr_queries", "arguments": {"site": "texte", "endDate": "texte", "startDate": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_gsc_opportunity_queries≈ 336 tokens

  Find queries where the site ranks on positions 8–20 (page 1 bottom / page 2), the "quick win" zone where small improvements can meaningfully increase clicks. Returns queries sorted by clicks descending (GSC API default). Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it. When several Google accounts are connected, the property is read through the account that can see it.

  Paramètres, retour & exemple (6)

  Paramètres

  • site · string · requis
    Property URL e.g. "https://example.com"
  • endDate · string · requis
    End date YYYY-MM-DD
  • rowLimit · number · optionnel
    Max rows (default 50, max 1000)
  • startDate · string · requis
    Start date YYYY-MM-DD
  • maxPosition · number · optionnel
    Maximum average position (default 20)
  • minPosition · number · optionnel
    Minimum average position (default 8)

  Exemple d'appel

  {"name": "get_gsc_opportunity_queries", "arguments": {"site": "texte", "endDate": "texte", "startDate": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_gsc_page_queries≈ 284 tokens

  Get search queries driving traffic to a specific page. Useful for understanding what a page ranks for. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it. When several Google accounts are connected, the property is read through the account that can see it.

  Paramètres, retour & exemple (5)

  Paramètres

  • page · string · requis
    Full page URL e.g. "https://example.com/blog/post"
  • site · string · requis
    Property URL e.g. "https://example.com"
  • endDate · string · requis
    End date YYYY-MM-DD
  • rowLimit · number · optionnel
    Max rows (default 25, max 1000)
  • startDate · string · requis
    Start date YYYY-MM-DD

  Exemple d'appel

  {"name": "get_gsc_page_queries", "arguments": {"page": "texte", "site": "texte", "endDate": "texte", "startDate": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_gsc_page_segment≈ 312 tokens

  Analyze search performance for a URL segment, e.g. all blog posts ("/blog/"), all product pages ("/products/"), or all docs ("/docs/"). Returns the top pages within that segment by clicks. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it. When several Google accounts are connected, the property is read through the account that can see it.

  Paramètres, retour & exemple (5)

  Paramètres

  • site · string · requis
    Property URL e.g. "https://example.com"
  • endDate · string · requis
    End date YYYY-MM-DD
  • rowLimit · number · optionnel
    Max rows (default 25, max 1000)
  • startDate · string · requis
    Start date YYYY-MM-DD
  • urlPattern · string · requis
    URL substring to filter by e.g. "/blog/" or "/products/"

  Exemple d'appel

  {"name": "get_gsc_page_segment", "arguments": {"site": "texte", "endDate": "texte", "startDate": "texte", "urlPattern": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_gsc_page_trend≈ 293 tokens

  Get daily click/impression/CTR/position trend for a specific page. Use this to see how a single page's search performance has changed over time, useful for measuring the impact of a content update or spotting a ranking drop. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it. When several Google accounts are connected, the property is read through the account that can see it.

  Paramètres, retour & exemple (4)

  Paramètres

  • page · string · requis
    Full page URL e.g. "https://example.com/blog/post"
  • site · string · requis
    Property URL e.g. "https://example.com"
  • endDate · string · requis
    End date YYYY-MM-DD
  • startDate · string · requis
    Start date YYYY-MM-DD

  Exemple d'appel

  {"name": "get_gsc_page_trend", "arguments": {"page": "texte", "site": "texte", "endDate": "texte", "startDate": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_gsc_properties≈ 153 tokens

  List all Google Search Console properties (sites) connected to this account. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it. When several Google accounts are connected, the properties visible to any of them are listed once each.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_gsc_properties", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_gsc_query_page_pairs≈ 286 tokens

  Get query+page combinations: which exact queries are landing on which pages. Essential for detecting keyword cannibalization (multiple pages competing for the same query) and understanding the search funnel. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it. When several Google accounts are connected, the property is read through the account that can see it.

  Paramètres, retour & exemple (4)

  Paramètres

  • site · string · requis
    Property URL e.g. "https://example.com"
  • endDate · string · requis
    End date YYYY-MM-DD
  • rowLimit · number · optionnel
    Max rows (default 100, max 1000)
  • startDate · string · requis
    Start date YYYY-MM-DD

  Exemple d'appel

  {"name": "get_gsc_query_page_pairs", "arguments": {"site": "texte", "endDate": "texte", "startDate": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_gsc_query_pages≈ 286 tokens

  Get all pages that rank for a specific search query. Useful for identifying which pages compete for the same keyword. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it. When several Google accounts are connected, the property is read through the account that can see it.

  Paramètres, retour & exemple (5)

  Paramètres

  • site · string · requis
    Property URL e.g. "https://example.com"
  • query · string · requis
    Search query to look up e.g. "best seo tools"
  • endDate · string · requis
    End date YYYY-MM-DD
  • rowLimit · number · optionnel
    Max rows (default 25, max 1000)
  • startDate · string · requis
    Start date YYYY-MM-DD

  Exemple d'appel

  {"name": "get_gsc_query_pages", "arguments": {"site": "texte", "query": "texte", "endDate": "texte", "startDate": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_gsc_query_trend≈ 276 tokens

  Get daily click/impression/CTR/position trend for a specific search query. Use this to track how a particular keyword's ranking and traffic evolves over time. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it. When several Google accounts are connected, the property is read through the account that can see it.

  Paramètres, retour & exemple (4)

  Paramètres

  • site · string · requis
    Property URL e.g. "https://example.com"
  • query · string · requis
    Search query to track e.g. "best seo tools"
  • endDate · string · requis
    End date YYYY-MM-DD
  • startDate · string · requis
    Start date YYYY-MM-DD

  Exemple d'appel

  {"name": "get_gsc_query_trend", "arguments": {"site": "texte", "query": "texte", "endDate": "texte", "startDate": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_gsc_search_appearance≈ 262 tokens

  Break down traffic by how the site appears in Google Search: organic web results, rich results, AMP, image search, video, news, etc. Shows which search features are driving impressions and clicks. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it. When several Google accounts are connected, the property is read through the account that can see it.

  Paramètres, retour & exemple (3)

  Paramètres

  • site · string · requis
    Property URL e.g. "https://example.com"
  • endDate · string · requis
    End date YYYY-MM-DD
  • startDate · string · requis
    Start date YYYY-MM-DD

  Exemple d'appel

  {"name": "get_gsc_search_appearance", "arguments": {"site": "texte", "endDate": "texte", "startDate": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_gsc_sitemaps≈ 200 tokens

  List all submitted sitemaps for a property, including submission date, last download time, URL counts, and any errors or warnings. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it. When several Google accounts are connected, the property is read through the account that can see it.

  Paramètres, retour & exemple (1)

  Paramètres

  • site · string · requis
    Property URL e.g. "https://example.com"

  Exemple d'appel

  {"name": "get_gsc_sitemaps", "arguments": {"site": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_gsc_top_pages≈ 256 tokens

  Get the top pages on a site by clicks from Google Search, with impressions, CTR, and average position. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it. When several Google accounts are connected, the property is read through the account that can see it.

  Paramètres, retour & exemple (4)

  Paramètres

  • site · string · requis
    Property URL e.g. "https://example.com"
  • endDate · string · requis
    End date YYYY-MM-DD
  • rowLimit · number · optionnel
    Max rows (default 25, max 1000)
  • startDate · string · requis
    Start date YYYY-MM-DD

  Exemple d'appel

  {"name": "get_gsc_top_pages", "arguments": {"site": "texte", "endDate": "texte", "startDate": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_gsc_top_queries≈ 274 tokens

  Get the top search queries driving traffic to a site, ordered by clicks. Shows clicks, impressions, CTR, and average position for each query. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it. When several Google accounts are connected, the property is read through the account that can see it.

  Paramètres, retour & exemple (4)

  Paramètres

  • site · string · requis
    Property URL e.g. "https://example.com" or "sc-domain:example.com"
  • endDate · string · requis
    End date YYYY-MM-DD
  • rowLimit · number · optionnel
    Max rows (default 25, max 1000)
  • startDate · string · requis
    Start date YYYY-MM-DD

  Exemple d'appel

  {"name": "get_gsc_top_queries", "arguments": {"site": "texte", "endDate": "texte", "startDate": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_gsc_url_inspection≈ 241 tokens

  Inspect a specific URL's indexing status in Google Search. Returns whether the page is indexed, coverage state, last crawl time, mobile usability, and rich results status. Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations to connect it. When several Google accounts are connected, the property is read through the account that can see it.

  Paramètres, retour & exemple (2)

  Paramètres

  • url · string · requis
    Full URL to inspect e.g. "https://example.com/blog/post"
  • site · string · requis
    Property URL e.g. "https://example.com"

  Exemple d'appel

  {"name": "get_gsc_url_inspection", "arguments": {"url": "texte", "site": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_internal_links≈ 118 tokens

  Get internal link structure for a domain (v1 stub)

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · number · optionnel
  • domain · string · requis

  Exemple d'appel

  {"name": "get_internal_links", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_keyword_rank_history≈ 537 tokens

  Get the stored day-by-day ranking history for one keyword on one search engine over a date range. Reads RankParse snapshots synced on a schedule; it is not a live SERP check. History is inherently single-engine, so engine is required (use get_keyword_rankings first to compare across engines). Days with no synced data are simply absent from rows rather than filled with a zero or placeholder value -- do not treat a missing date as "not ranking". Bing and Yandex are opt-in and lower-frequency than Google; their responses may report availability as provider_limited, meaning that provider did not return enough data for that day rather than the keyword ranking nowhere.

  Paramètres, retour & exemple (6)

  Paramètres

  • engine · string · requis · google | bing | yandex
    Search engine to get history for (required -- history is always single-engine)
  • site_id · string · requis
    Logical RankParse website ID, from list_rank_tracking_sites
  • end_date · string · requis
    End of the range, inclusive, as YYYY-MM-DD
  • dimension · string · optionnel · total | device
    Breakdown of the daily rows. Default "total" is one row per day; "device" is one row per day per device (desktop/mobile/tablet) with a device field on each row. Device rows exist only where the provider synced them (always for Google; Yandex only when its device breakdown is enabled), so an empty device history for a keyword with total history means "not synced per-device", not "no traffic".
  • keyword_id · string · requis
    Tracked keyword ID, from list_tracked_keywords
  • start_date · string · requis
    Start of the range, inclusive, as YYYY-MM-DD

  Exemple d'appel

  {"name": "get_keyword_rank_history", "arguments": {"engine": "google", "site_id": "texte", "end_date": "texte", "keyword_id": "texte", "start_date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_keyword_rankings≈ 574 tokens

  Get stored ranking summaries (current vs previous period) for a website's tracked keywords across Google, Bing, and Yandex. Reads RankParse snapshots synced on a schedule; it is not a live SERP check. Positions are provider-reported averages over each engine's own returned period and are NOT comparable as one blended rank across engines -- compare per engine, not by averaging across them. A missing engine in a keyword's response means that engine is not connected/attached for this site (check enabled_engines in the response), not a zero or bottom rank. Bing and Yandex are opt-in and many accounts do not have them connected, so their absence is normal, not an error. Each present engine also carries an availability field; a null current/previous position with availability other than "available" (e.g. provider_limited, which Bing/Yandex may report, or pending_first_sync, stale, sync_failed) means a data quality/sync issue for that engine, not evidence the keyword ranks nowhere.

  Paramètres, retour & exemple (6)

  Paramètres

  • limit · integer · optionnel
    Max keywords to return (default 100, max 100)
  • engine · string · optionnel · all | google | bing | yandex
    Search engine to report on. Defaults to "all" (every engine enabled for this account) -- the primary use case is comparing engines side by side, so leave this unset unless you need one engine only.
  • offset · integer · optionnel
    Pagination offset (default 0)
  • site_id · string · requis
    Logical RankParse website ID, from list_rank_tracking_sites
  • keyword_id · string · optionnel
    Restrict to one tracked keyword ID, from list_tracked_keywords. Omit to get all keywords for the site.
  • period_days · integer · optionnel
    Length of the current/previous comparison window in days (default 28, max 90)

  Exemple d'appel

  {"name": "get_keyword_rankings", "arguments": {"site_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_link_audit≈ 158 tokens

  Audit a domain's backlink profile: health score, risk flags, link quality breakdown, anchor text profile, top and risky backlinks, and outbound link summary. Scores are derived from a sample of the 250 most recent backlinks, not the full profile.

  Paramètres, retour & exemple (1)

  Paramètres

  • domain · string · requis

  Exemple d'appel

  {"name": "get_link_audit", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_link_intersect≈ 119 tokens

  Find domains linking to A but not B

  Paramètres, retour & exemple (2)

  Paramètres

  • domain_a · string · requis
  • domain_b · string · requis

  Exemple d'appel

  {"name": "get_link_intersect", "arguments": {"domain_a": "texte", "domain_b": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_link_velocity≈ 109 tokens

  Get rate of new/lost links over time (v1 stub)

  Paramètres, retour & exemple (1)

  Paramètres

  • domain · string · requis

  Exemple d'appel

  {"name": "get_link_velocity", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_lost_links≈ 108 tokens

  Get links lost since previous crawl (v1 stub)

  Paramètres, retour & exemple (1)

  Paramètres

  • domain · string · requis

  Exemple d'appel

  {"name": "get_lost_links", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_new_links≈ 108 tokens

  Get links gained since previous crawl (v1 stub)

  Paramètres, retour & exemple (1)

  Paramètres

  • domain · string · requis

  Exemple d'appel

  {"name": "get_new_links", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_outbound_links≈ 116 tokens

  Get domains that a domain links out to

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · number · optionnel
  • domain · string · requis

  Exemple d'appel

  {"name": "get_outbound_links", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_page_performance≈ 201 tokens

  Google PageSpeed Insights report for a URL: Lighthouse performance/accessibility/SEO scores and Core Web Vitals (LCP, CLS, INP, FCP, TTFB), with lab and field (CrUX) data. Defaults to mobile; pass strategy=desktop for the desktop profile. Subject to a per-user daily cap (50/day) and a service-wide daily cap; successful responses are cached for 24h.

  Paramètres, retour & exemple (2)

  Paramètres

  • url · string · requis
  • strategy · string · optionnel · mobile | desktop

  Exemple d'appel

  {"name": "get_page_performance", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_page_seo≈ 144 tokens

  Full real-time SEO audit for a URL: title/description with length checks, canonical, robots meta, OG tags, Twitter cards, JSON-LD, hreflang, headings, images missing alt, link counts, word count

  Paramètres, retour & exemple (1)

  Paramètres

  • url · string · requis

  Exemple d'appel

  {"name": "get_page_seo", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_platform_domains≈ 291 tokens

  Get all domains running a specific platform or technology (e.g. WordPress, Shopify, Wix, Squarespace, Framer). Returns domains with DA scores. Billed at 1 credit per result returned.

  Paramètres, retour & exemple (6)

  Paramètres

  • tld · string · optionnel
    Filter by top-level domain (e.g. "com", "io", "co.uk")
  • sort · string · optionnel · da_desc | da_asc | domain_asc
    Sort order: da_desc (default), da_asc, domain_asc
  • limit · number · optionnel
    Max results to return (default 100, max 1000)
  • max_da · number · optionnel
    Maximum domain authority score (0–100)
  • min_da · number · optionnel
    Minimum domain authority score (0–100)
  • platform · string · requis
    Platform name or slug (e.g. "wordpress", "shopify", "wix", "squarespace", "framer")

  Exemple d'appel

  {"name": "get_platform_domains", "arguments": {"platform": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_platform_trends≈ 111 tokens

  Get a ranked list of all detectable platforms and technologies with their domain counts, useful for comparing platform adoption (e.g. how many sites run WordPress vs Shopify)

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_platform_trends", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_rank_alert_settings≈ 193 tokens

  Get the rank-change alert configuration for one RankParse website: whether weekly alert digests are enabled (they are opt-in and default off), the moved_up/moved_down position threshold, and the optional digest email override. Delivery is Sunday at 18:00 UTC when meaningful changes exist.

  Paramètres, retour & exemple (1)

  Paramètres

  • site_id · string · requis
    Logical RankParse website ID, from list_rank_tracking_sites

  Exemple d'appel

  {"name": "get_rank_alert_settings", "arguments": {"site_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_referring_domains≈ 125 tokens

  Get unique domains linking to a domain

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · number · optionnel
  • score · boolean · optionnel
  • domain · string · requis

  Exemple d'appel

  {"name": "get_referring_domains", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_schema_markup≈ 133 tokens

  Extract schema.org JSON-LD structured data from a URL: every entity found (including ones nested in @graph), their types, and any malformed blocks

  Paramètres, retour & exemple (1)

  Paramètres

  • url · string · requis

  Exemple d'appel

  {"name": "get_schema_markup", "arguments": {"url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_similar_domains≈ 136 tokens

  Find domains with similar link profiles, useful for competitor discovery. May return partial results when the query fan-out hits time budget.

  Paramètres, retour & exemple (1)

  Paramètres

  • domain · string · requis

  Exemple d'appel

  {"name": "get_similar_domains", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_site_explorer≈ 118 tokens

  Full SEO overview for a domain (backlinks, authority, top pages, anchor text)

  Paramètres, retour & exemple (1)

  Paramètres

  • domain · string · requis

  Exemple d'appel

  {"name": "get_site_explorer", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_site_health≈ 143 tokens

  Real-time site health check: HTTPS enforcement, HSTS, www redirect behavior, key URL availability and response times, security headers (CSP, X-Frame-Options, HSTS), robots.txt analysis

  Paramètres, retour & exemple (1)

  Paramètres

  • domain · string · requis

  Exemple d'appel

  {"name": "get_site_health", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_sitemap≈ 124 tokens

  Discover and parse a domain's sitemap. Returns URLs with lastmod, changefreq, and priority

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · number · optionnel
  • domain · string · requis

  Exemple d'appel

  {"name": "get_sitemap", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_tech_stack≈ 130 tokens

  Real-time technology detection for a domain: frameworks, CMS, analytics, CDN, hosting, e-commerce, payments, and more (50+ technologies)

  Paramètres, retour & exemple (1)

  Paramètres

  • domain · string · requis

  Exemple d'appel

  {"name": "get_tech_stack", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_top_pages≈ 113 tokens

  Get most-linked pages for a domain

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · number · optionnel
  • domain · string · requis

  Exemple d'appel

  {"name": "get_top_pages", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_proposals≈ 252 tokens

  List actions you or RankParse proposed and their status (pending, approved, succeeded, failed, skipped, expired). Use it to see what the user approved or skipped. A failed or partly failed proposal carries an error_code, for example nothing_to_send (everything was already queued or suppressed), payload_changed_since_approval (it changed after approval, so propose again) or approver_lost_permission (tell the user).

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · integer · optionnel
  • status · string · optionnel · pending | approved | executing | succeeded | partially_succeeded | failed | skipped | expired
  • site_id · string · optionnel

  Exemple d'appel

  {"name": "list_proposals", "arguments": {"limit": 1, "status": "pending", "site_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_rank_change_alerts≈ 322 tokens

  List recent rank-change alert events for one RankParse website: significant stored-ranking moves (entered/left top 3 or top 10, moved up/down past the configured threshold, new/lost rankings) detected daily and summarized in a weekly email. Reads recorded events, never runs a live check; a keyword with no events simply had no significant moves. Events exist only while alerts are enabled for the site (see get_rank_alert_settings) and only for engines whose data was actually available -- provider-limited or pending engines generate nothing rather than false "lost ranking" alerts.

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · integer · optionnel
    Max events to return (default 100, max 100)
  • offset · integer · optionnel
    Pagination offset (default 0)
  • site_id · string · requis
    Logical RankParse website ID, from list_rank_tracking_sites

  Exemple d'appel

  {"name": "list_rank_change_alerts", "arguments": {"site_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_rank_tracking_sites≈ 126 tokens

  List websites configured for stored Google, Bing, and Yandex keyword tracking, including provider freshness and sync state. This reads RankParse snapshots; it does not run a live SERP check.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_rank_tracking_sites", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_tracked_keywords≈ 203 tokens

  List the tracked keyword IDs and text for one RankParse website. Call list_rank_tracking_sites first to obtain site_id.

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · integer · optionnel
    Max keywords to return (default 100, max 100)
  • offset · integer · optionnel
    Pagination offset (default 0)
  • site_id · string · requis
    Logical RankParse website ID, from list_rank_tracking_sites

  Exemple d'appel

  {"name": "list_tracked_keywords", "arguments": {"site_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_websites≈ 122 tokens

  List this account's websites (id, host, name). Use the id as site_id in propose_* and log_activity. At the start of any RankParse session, call get_agent_tasks to see work the user queued for you.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_websites", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• log_activity≈ 213 tokens

  Record what you did for the user in their RankParse activity feed, in plain text (max 500 characters). Credits are taken from your recent RankParse calls automatically; do not report credits yourself. Pass client_request_id to make retries safe.

  Paramètres, retour & exemple (4)

  Paramètres

  • site_id · string · optionnel
  • summary · string · requis
  • kind_hint · string · optionnel · research | draft | analysis
  • client_request_id · string · optionnel

  Exemple d'appel

  {"name": "log_activity", "arguments": {"summary": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• outreach_add_contacts≈ 582 tokens

  Add contacts with per-contact email copy to a campaign (max 100 per call, 500 per campaign, one contact per domain). Works on a draft campaign AND on an already-launched one, which is how you top a live campaign up with fresh prospects. Each contact needs a researched, real email address (never guess addresses) plus a personalized subject and plain-text body (subject ≤500 chars, body ≤10,000). Write like a human: plain punctuation, and NEVER use em-dashes in subjects or bodies. Subjects must be 2-5 words that read like a note from a colleague and reference their content (e.g. "your AI tools guide"): never sales words like exclusive, lifetime, revenue, or deal. Internationalized (non-ASCII) domains must be given in punycode (xn--) form. Returns how many were added and which were skipped (invalid email, duplicate domain/email, copy too long, campaign full, already_contacted = this person was emailed in an earlier campaign). Contacts added to a launched campaign sit inert until you call outreach_launch_campaign again.

  Paramètres, retour & exemple (2)

  Paramètres

  • contacts · array · requis
    Contacts with their personalized copy
  • campaign_id · string · requis
    Campaign id from outreach_create_campaign

  Exemple d'appel

  {"name": "outreach_add_contacts", "arguments": {"contacts": [], "campaign_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• outreach_configure_sending≈ 419 tokens

  Update the Gmail sending schedule: max_sends_per_day (1-100, applies account-wide across all campaigns) and/or auto_send_enabled (false stops ALL sending, true resumes it). Lowering the cap or turning sending off applies immediately. For most accounts, raising the cap or turning sending on needs the user's approval in RankParse: the response is 202 with ok true, status awaiting_approval and a review_url, and nothing has been increased yet, so show the user the review_url. For other accounts a raise applies directly and returns ok true. A request that mixes both applies the decrease or disable now and proposes the rest; the message then starts "Applied now: ...". If it fails with change_in_progress, another sending change is already approved or running. The increase was not applied, but any decrease or disable in the same request has been applied (see applied and message): send the increase again after it completes (check list_proposals). If status is approved, it is already approved; do not ask again. Confirm with the user before changing these; they control real email volume.

  Paramètres, retour & exemple (2)

  Paramètres

  • auto_send_enabled · boolean · optionnel
    Master switch for the hourly send sweep
  • max_sends_per_day · integer · optionnel
    Daily send cap across all campaigns (1-100)

  Exemple d'appel

  {"name": "outreach_configure_sending", "arguments": {"auto_send_enabled": true, "max_sends_per_day": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• outreach_create_campaign≈ 541 tokens

  Create a draft link-building outreach campaign (sends via the user's connected Gmail). Outreach flow: 1) interview the user (their site, goal, competitors), 2) build a prospect list with get_competitor_gap / get_referring_domains / get_domain_authority, 3) research one real contact email per prospect domain, 4) write a short personalized subject+body per contact, 5) outreach_create_campaign, 6) outreach_add_contacts, 7) show the user the emails you drafted and get their OK before launching, 8) outreach_launch_campaign: this tells RankParse the campaign is ready and returns status ready_for_review with a review_url (the campaign page), and nothing is sent until the user approves the emails there one by one; tell the user it is ready to review in RankParse and share the review_url (if status is approved it is already approved, so do not launch again). Shortcut: propose_outreach_send does steps 5, 6 and 8 in one call (creates or tops up the campaign, adds the contacts, marks it ready for review). Requires the user to have Gmail connected at rankparse.com/dashboard/integrations. To CONTINUE an existing campaign rather than start a new one, begin at outreach_suggest_prospects instead of step 1: campaigns are topped up, not replaced.

  Paramètres, retour & exemple (4)

  Paramètres

  • goal · string · optionnel
    What the outreach is trying to achieve, for the campaign record
  • name · string · requis
    Campaign name, e.g. "SaaS blogs - competitor gap Aug 2026"
  • site_id · string · optionnel
    Optional RankParse website id (from list_websites, or given to you in a website-scoped outreach prompt) to link this campaign to a website. Omit to leave it unassigned.
  • your_domain · string · requis
    The domain being promoted, e.g. "example.com"

  Exemple d'appel

  {"name": "outreach_create_campaign", "arguments": {"name": "texte", "your_domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• outreach_get_campaign≈ 143 tokens

  Get a campaign's status and delivery counts (awaiting launch, queued, sending, sent, skipped). Use to answer "how is my campaign doing?".

  Paramètres, retour & exemple (1)

  Paramètres

  • campaign_id · string · requis
    Campaign id

  Exemple d'appel

  {"name": "outreach_get_campaign", "arguments": {"campaign_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• outreach_launch_campaign≈ 306 tokens

  Tell RankParse a campaign's emails are ready. It returns status ready_for_review with a review_url (the campaign page): the user reviews and approves each email there, and nothing is sent until they do. Only if the user turned on "Let Claude send without review" in RankParse does it queue the emails directly (queued/suppressed counts). Safe to call again; it never re-sends. When it returns ready_for_review, tell the user the emails are ready to review in RankParse and show them the review_url. If status is approved, it is already approved; do not launch again. If it returns queued/suppressed counts instead of ready_for_review, the emails are being sent now, so only call it after the user has seen the drafted emails and explicitly approved sending.

  Paramètres, retour & exemple (1)

  Paramètres

  • campaign_id · string · requis
    Campaign id to launch

  Exemple d'appel

  {"name": "outreach_launch_campaign", "arguments": {"campaign_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• outreach_list_campaigns≈ 156 tokens

  List this account's outreach campaigns with status and contact counts. Optionally filter to one website; an unknown site_id returns an empty list.

  Paramètres, retour & exemple (1)

  Paramètres

  • site_id · string · optionnel
    Optional RankParse website id (from list_websites) to list only that website's campaigns

  Exemple d'appel

  {"name": "outreach_list_campaigns", "arguments": {"site_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• outreach_pause_campaign≈ 148 tokens

  Pause one campaign: its queued emails stop sending but stay queued, so resuming continues exactly where it left off. Other campaigns keep sending.

  Paramètres, retour & exemple (1)

  Paramètres

  • campaign_id · string · requis
    Campaign id to pause

  Exemple d'appel

  {"name": "outreach_pause_campaign", "arguments": {"campaign_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• outreach_resume_campaign≈ 136 tokens

  Resume a paused campaign; its queued emails become eligible for the next hourly send sweep again.

  Paramètres, retour & exemple (1)

  Paramètres

  • campaign_id · string · requis
    Campaign id to resume

  Exemple d'appel

  {"name": "outreach_resume_campaign", "arguments": {"campaign_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• outreach_sending_status≈ 128 tokens

  Get the Gmail sending pipeline status: connected account, auto-send on/off, daily cap, how many sent today, remaining budget today, total queued across campaigns, and estimated days to drain the queue.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "outreach_sending_status", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• outreach_suggest_prospects≈ 343 tokens

  START HERE when adding more websites to an existing campaign. Returns the campaign's own context (domain, goal), how much room it has left, its send queue, and — critically — exclude_domains: every prospect domain this account has already used in ANY campaign. You MUST filter your discovery results against exclude_domains. get_competitor_gap is cached and unpaginated, so calling it again returns the identical top-N: request a limit several times larger than recommended_batch_size, drop everything already in exclude_domains, and keep what is left. Widen the pool with get_similar_domains, get_link_intersect, or get_platform_domains when the competitor gap is exhausted. Then research one real contact per surviving domain, call outreach_add_contacts, and finish with outreach_launch_campaign to queue them. Note exclude_domains_truncated: when true the list is capped and you should prefer clearly-unseen domains.

  Paramètres, retour & exemple (1)

  Paramètres

  • campaign_id · string · requis
    Campaign id to top up

  Exemple d'appel

  {"name": "outreach_suggest_prospects", "arguments": {"campaign_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• propose_indexnow_submit≈ 260 tokens

  Ask the user to approve submitting URLs to IndexNow (Bing, Yandex, Seznam, Naver). All URLs on one host that is one of the user's websites, max 1000. Costs 1 credit only when it runs. If status is approved, it is already approved; do not propose it again. Nothing happens until the user approves it in RankParse (unless they allowed it in website settings). Show them the review_url.

  Paramètres, retour & exemple (3)

  Paramètres

  • note · string · optionnel
    Why, in one or two plain sentences. Shown to the user labelled as your note.
  • urls · array · requis
  • site_id · string · optionnel

  Exemple d'appel

  {"name": "propose_indexnow_submit", "arguments": {"urls": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• propose_outreach_send≈ 537 tokens

  Put outreach emails in front of the user for review. Pass contacts inline (max 100, one per domain, researched real addresses, personalized subject and plain-text body, no em-dashes). RankParse creates or tops up the draft campaign and marks it ready: the user reviews and approves each email on the campaign page (the review_url), and nothing is sent until they do. Use site_id from list_websites (required when creating a campaign; with campaign_id it must match that campaign's website). To propose the copy-ready contacts a campaign already has, pass campaign_id without contacts. If status is approved, it is already approved; do not propose it again. Nothing is sent until the user approves it in RankParse. Show them the review_url.

  Paramètres, retour & exemple (5)

  Paramètres

  • note · string · optionnel
    Why, in one or two plain sentences. Shown to the user labelled as your note.
  • site_id · string · optionnel
    Website id from list_websites. Required when campaign_id is omitted
  • contacts · array · optionnel
    Required when campaign_id is omitted
  • campaign_id · string · optionnel
    Existing campaign to top up; omit to create one
  • campaign_name · string · optionnel
    Required when campaign_id is omitted

  Exemple d'appel

  {"name": "propose_outreach_send", "arguments": {"note": "texte", "site_id": "texte", "contacts": [], "campaign_id": "texte", "campaign_name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• provision_indexnow_key≈ 226 tokens

  Get (or create) the IndexNow key for a host. Idempotent per host: repeated calls return the same key. Free (0 credits). Returns the key, its required key_location (https://<host>/<key>.txt), and verified (whether the hosted key file has already been confirmed). The USER must host a UTF-8 text file containing exactly the key at key_location before submit_indexnow_urls will work — tell them the location and the key, then submit.

  Paramètres, retour & exemple (1)

  Paramètres

  • domain · string · requis
    The website host to provision a key for, e.g. "example.com"

  Exemple d'appel

  {"name": "provision_indexnow_key", "arguments": {"domain": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• submit_indexnow_urls≈ 249 tokens

  Submit changed/new/deleted URLs to IndexNow so search engines (Bing, Yandex, Seznam, Naver, ...) recrawl them promptly. All URLs must share one host, max 1000 per call. Requires the host's IndexNow key file to be live: call provision_indexnow_key first and make sure the user hosted the key file at its key_location (indexnow_key_not_verified means the file is missing or wrong). Costs 1 credit, refunded automatically when the submission fails.

  Paramètres, retour & exemple (1)

  Paramètres

  • urls · array · requis
    Full URLs to submit, e.g. ["https://example.com/a", "https://example.com/b"] — all on the same host

  Exemple d'appel

  {"name": "submit_indexnow_urls", "arguments": {"urls": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• update_rank_alert_settings≈ 332 tokens

  Update rank-change alert settings for one RankParse website: enable/disable the weekly digest (opt-in, default off), set the moved_up/moved_down position threshold (1-50, default 5), or set/clear an email override for that site's digest lines (null reverts to the account email). Only the fields you pass change. Confirm with the user before enabling -- this turns on a real weekly email when meaningful changes exist.

  Paramètres, retour & exemple (4)

  Paramètres

  • enabled · boolean · optionnel
    Turn the weekly alert digest on or off for this site
  • site_id · string · requis
    Logical RankParse website ID, from list_rank_tracking_sites
  • email_override · string|null · optionnel
    Email address to send this site's digest lines to instead of the account email; null clears it
  • move_threshold · number · optionnel
    Average-position delta that counts as moved_up/moved_down (default 5)

  Exemple d'appel

  {"name": "update_rank_alert_settings", "arguments": {"site_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• zeekeo_activate_campaign≈ 250 tokens

  Activates a paused Zeekeo campaign so it starts running (sends real LinkedIn connection invites per the campaign's configured limit/delay). Zeekeo campaigns are created paused by default — call this after zeekeo_create_campaign to actually start sending. This resumes REAL LinkedIn automation — confirm with the user before calling. Requires the user to have connected their own Zeekeo Launchpad account. Direct them to rankparse.com/dashboard/integrations to connect it.

  Paramètres, retour & exemple (1)

  Paramètres

  • campaign_id · string · requis
    Zeekeo campaign id from zeekeo_list_campaigns or zeekeo_create_campaign

  Exemple d'appel

  {"name": "zeekeo_activate_campaign", "arguments": {"campaign_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• zeekeo_create_campaign≈ 618 tokens

  Creates a Zeekeo LinkedIn campaign: sends a connection invite using invite_template_id, and optionally — if followup_template_id is given — waits for the invite to be accepted, then sends a follow-up message using that template. Create templates first with zeekeo_create_template. Provide exactly one of filter_url (a LinkedIn search results URL) or profile_urls (specific profiles) as the target. This starts REAL LinkedIn automation once the campaign has profiles in it — confirm with the user before calling. Requires the user to have connected their own Zeekeo Launchpad account. Direct them to rankparse.com/dashboard/integrations to connect it.

  Paramètres, retour & exemple (10)

  Paramètres

  • name · string · requis
    Campaign name
  • filter_url · string · optionnel
    A LinkedIn search results URL to source profiles from. Provide this or profile_urls, not both.
  • invite_delay · number · optionnel
    Seconds to wait before the first invite (default 0)
  • invite_limit · number · optionnel
    Max invites to send (default 20)
  • profile_urls · array · optionnel
    Specific LinkedIn profile URLs to target. Provide this or filter_url, not both.
  • invite_template_id · string · requis
    Template id from zeekeo_create_template (type linkedin_invite)
  • followup_delay_hours · number · optionnel
    Hours to wait after connection before the follow-up (default 24)
  • followup_template_id · string · optionnel
    Template id from zeekeo_create_template (type linkedin_message) for a follow-up message sent after the invite is accepted. Omit for an invite-only campaign. Must be a linkedin_message template — email_message and linkedin_inmail templates are not valid here.
  • exclude_past_campaigns_targets · boolean · optionnel
    Skip people already targeted in a previous campaign (default true)
  • exclude_first_degree_connections · boolean · optionnel
    Skip people already connected to the user (default true)

  Exemple d'appel

  {"name": "zeekeo_create_campaign", "arguments": {"name": "texte", "invite_template_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• zeekeo_create_template≈ 337 tokens

  Creates a reusable Zeekeo message template. Call this BEFORE zeekeo_create_campaign — a campaign references templates by the template_id this returns, not inline text. type must be 'linkedin_invite' for a connection-request template, or one of linkedin_message/linkedin_inmail/email_message for a follow-up/reply template. Requires the user to have connected their own Zeekeo Launchpad account. Direct them to rankparse.com/dashboard/integrations to connect it.

  Paramètres, retour & exemple (4)

  Paramètres

  • body · string · requis
    Message text. Supports Zeekeo merge variables like {{FIRST_NAME}} and {{COMPANY}}.
  • name · string · requis
    Template name, for your own reference in the Zeekeo dashboard
  • type · string · requis · linkedin_invite | linkedin_message | linkedin_inmail | email_message
    What kind of message this template is for
  • subject · string · optionnel
    Subject line, required when type is email_message

  Exemple d'appel

  {"name": "zeekeo_create_template", "arguments": {"body": "texte", "name": "texte", "type": "linkedin_invite"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• zeekeo_list_campaigns≈ 154 tokens

  List the user's Zeekeo Launchpad campaigns (LinkedIn automation). Use this to find a campaign_id for zeekeo_send_message, or call zeekeo_create_campaign to make a new one. Requires the user to have connected their own Zeekeo Launchpad account. Direct them to rankparse.com/dashboard/integrations to connect it.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "zeekeo_list_campaigns", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• zeekeo_send_message≈ 356 tokens

  Sends a REAL LinkedIn message, InMail, or email through Zeekeo Launchpad to a profile in one of the user's existing Zeekeo campaigns. Only call this after showing the user the drafted message and getting explicit approval. Resolves linkedin_url into that campaign first, so the profile must be reachable from it (use zeekeo_list_campaigns to pick campaign_id). Requires the user to have connected their own Zeekeo Launchpad account. Direct them to rankparse.com/dashboard/integrations to connect it.

  Paramètres, retour & exemple (5)

  Paramètres

  • body · string · requis
    Message text
  • type · string · requis · linkedin_message | linkedin_inmail | email_message
    Channel to send through
  • subject · string · optionnel
    Subject line, required when type is email_message
  • campaign_id · string · requis
    Zeekeo campaign id from zeekeo_list_campaigns
  • linkedin_url · string · requis
    LinkedIn profile URL or public identifier of the recipient

  Exemple d'appel

  {"name": "zeekeo_send_message", "arguments": {"body": "texte", "type": "linkedin_message", "campaign_id": "texte", "linkedin_url": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.rankparse.com/mcp