AdsBot-Google-MobileGoogle's special-case crawlers page names AdsBot-Google-Mobile as the robots.txt token for AdsBot Mobile Web. The page says the global user agent (*) is ignored. Crawling preferences for this token affect Google Ads' ability to check web page ad quality. A retired iPhone string on the same page used this same token and is no longer in use. AdsBot-Google is a different token. This check matches the whole token and still reports the RFC 9309 decision.
ads_checkignores_star. The vendor says this robot does not take the general User-agent: * rules in robots.txt into account.Mozilla/5.0 (Linux; Android 6.0.1; Nexus 5X Build/MMB29P) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/W.X.Y.Z Mobile Safari/537.36 (compatible; AdsBot-Google-Mobile; +http://www.google.com/mobile/adsbot.html) Chrome/W.X.Y.Z is the page's placeholder. The same page lists a retired iPhone string that uses this same robots.txt token and is no longer in use: Mozilla/5.0 (iPhone; CPU iPhone OS 14_7_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/14.1.2 Mobile/15E148 Safari/604.1 (compatible; AdsBot-Google-Mobile; +http://www.google.com/mobile/adsbot.html).curl -s https://whosthatbot.com/v1/crawlers/adsbot-google-mobile
tools/call with name check_robots is the same check at POST /mcp. The pasted file disallows AdsBot-Google-Mobile on /docs and allows *. The call does not fetch a host.
curl -s https://whosthatbot.com/mcp -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"check_robots","arguments":{"robots_txt":"User-agent: AdsBot-Google-Mobile\nDisallow: /\n\nUser-agent: *\nAllow: /\n","path":"/docs","ids":["adsbot-google-mobile"]}}}'
That call returns fetched_target false. This row is disallow via group AdsBot-Google-Mobile, rule Disallow: /.