Your account · free to readAsk your AI which queries you are losing, and why.
The queries and pages that earn your organic clicks, average position day by day, any breakdown by query, page, country or device, and how Google sees a single URL — answered inside ChatGPT, Claude, Codex or Cursor. Connect your Search Console property to toolfare once; your AI reads it with your own login, and every read is free.
1Connect your AI app
Pick the app you use. You do this once, and every API on toolfare is then available in it.
Add toolfare as a connector in Claude
Add to Claudehttps://api.toolfare.ai/mcp
- 1Open Customize → Connectors and choose "Add custom connector".
- 2Paste this URL as the remote MCP server URL.
- 3Leave the OAuth client id and secret under Advanced settings empty.
- 4Complete the browser authorization, then return to your conversation.
Custom connectors are available on Free, Pro, Max, Team and Enterprise. A Free account may hold one custom connector in total.
Claude’s own instructions2What to ask
Copy a prompt into your AI app once you’re connected. It picks the right one of the 7 tools and tells you the price first.
The searches that bring people in
Top Google queries for a date range with clicks, impressions, click-through rate and average position.
- “What did people search to find us last month?”
- “Which queries get impressions but almost no clicks?”
The pages that earn organic clicks
Every URL with organic impressions and clicks over a date range, sorted by clicks, with its average position.
- “Which pages get the most clicks from Google?”
- “Which of our pages lost the most clicks this week?”
Any breakdown, with filters
Search performance grouped by any mix of query, page, country, device and date, filtered however you need — only queries containing your own name, only one country, image search instead of web.
- “Which queries does our pricing page rank for, by country?”
- “Show clicks by device for the last 28 days, leaving out queries with our own name in them.”
Clicks and position, day by day
A daily series of clicks, impressions, CTR and position for the property — the shape of a drop, with a date on it.
- “When did our organic clicks start falling?”
- “Chart our average position over the last three months.”
How Google sees one URL
Whether a page is indexed and why not, the canonical Google chose, the last crawl, mobile usability and rich-result status.
- “Is this page indexed, and if not, why?”
- “Which canonical did Google pick for this URL?”
Whether your sitemaps are healthy
Submitted sitemaps with their status, warnings, errors, and submitted against indexed counts.
- “Do any of our sitemaps have errors?”
- “How many submitted URLs are actually indexed?”
Also available: The Search Console properties your toolfare account can read
1Create an API key
One key and one endpoint for every API on toolfare.
export TOOLFARE_API_KEY='tf_live_…'
2Every tool and its input
Send the tool name and its arguments as JSON; the reply is JSON too.
gsc_list_top_queriesTop Google queries for a date range with clicks, impressions, click-through rate and average position.
gsc_list_top_pagesEvery URL with organic impressions and clicks over a date range, sorted by clicks, with its average position.
gsc_query_search_analyticsSearch performance grouped by any mix of query, page, country, device and date, filtered however you need — only queries containing your own name, only one country, image search instead of web.
gsc_get_daily_trendA daily series of clicks, impressions, CTR and position for the property — the shape of a drop, with a date on it.
gsc_inspect_urlWhether a page is indexed and why not, the canonical Google chose, the last crawl, mobile usability and rich-result status.
gsc_list_sitemapsSubmitted sitemaps with their status, warnings, errors, and submitted against indexed counts.
gsc_list_sitesThe Search Console properties your toolfare account can read
Use it when
- Organic traffic dropped and you want the queries and pages that moved.
- You want queries with impressions but few clicks — the titles worth rewriting.
- A page is not ranking and you want to know whether Google has even indexed it.
- You want position over time, not a single snapshot.
Look elsewhere when
- You want what the visitors did after landing. That is GA4. Use this instead
- You want who outranks you right now. Search Console only reports on your own property — ask a live results source. Use this instead
- You want a competitor’s keywords or backlinks. That is a third-party index. Use this instead
- You want to request indexing or submit a sitemap. This connection is read-only.
Google Search Console directly, or through toolfare
Directly
- The Search Console interface, 1,000 rows at a time
- A Google Cloud project and OAuth client for the API
- Your own code to join queries to pages to dates
Through toolfare
- Ask in the chat you already use, in plain English
- One toolfare login; no OAuth client handed to an agent
- Search Console beside GA4 and your ad accounts in the same question
You get reads, not Search Console. Nothing can be submitted, removed or reindexed through the MCP connection, and nothing is monitored for you between questions — if a page needs reindexing, you request it in Search Console.
Limits
- URL inspection is capped by Google at roughly 2,000 inspections a day per property, so it answers about specific pages, not a whole site.
- A property has to be addressed exactly as Search Console names it — a domain property and a URL-prefix property are different properties.
- Days with no organic activity are absent from the daily series rather than returned as zero.
- Only properties you connected are readable.