gsc_add_property
ChatGPTAdd a URL-prefix or Domain property to the Google Search Console property set of the user's connected Google login (Search Console's sites.add). site_url must be the exact form: sc-domain:example.com for a Domain property or https://example.com/ for a URL-prefix property — a bare domain is refused so the user chooses. Does not verify ownership: the answer reports the permission level Google gives the login afterwards, and an unverified property can be read or changed only after the user verifies it in Search Console. Adding a property already in the set changes nothing.
gsc_compare_periods
ChatGPTCompare organic Google Search performance of one Search Console property between two date windows: totals (clicks, impressions, CTR, position) for both with the change, and — when dimensions are given — the rows that gained and lost the most clicks (queries that fell, pages that grew, countries that shifted), each with both windows' figures and the delta. The previous window defaults to the same length immediately before the current one; pass previous_start_date and previous_end_date for year-over-year. Rows are ordered by the size of the click change; row_limit caps how many come back. Read-only.
gsc_delete_sitemap
ChatGPTRemove one sitemap submission from a Google Search Console property of the user's connected Google login (Search Console's sitemaps.delete), for example an old or duplicate sitemap. The sitemap must be in the property's submitted list (gsc_list_sitemaps); anything else changes nothing. The connected login needs Full user or Owner permission. Does not delete the sitemap file from the site, does not remove any URL from Google Search results, and does not stop Google from discovering those URLs by other means. Name the sitemap to the user and get their approval first.
gsc_find_keyword_opportunities
ChatGPTRank the organic search queries of one Search Console property by the clicks they could add, from the user's connected Google login's own data. Two lists: striking-distance queries (average position 4-20 with real impressions — within reach of the top 3 with content or internal-link work, ranked by the clicks a top-3 position would bring) and low-CTR queries (page-one position earning well under the CTR that position usually gets — the title or snippet is the problem). Each row carries clicks, impressions, CTR, position, the expected CTR and the potential extra clicks. Pass exclude_queries_containing with the brand name, page to look at one landing page, split_by_page to see which page each query lands on. Read-only; proposes nothing to Google Ads.
gsc_find_page_opportunities
ChatGPTFind the landing pages of one Search Console property that organic search work would move most, from the user's connected Google login's own data. Four lists: low-CTR pages (page-one average position earning well under the usual CTR — title and snippet), striking-distance pages (average position 4-20 across their queries — content and internal links), decaying pages (clicks down 30 % or more against the previous window of the same length) and cannibalised queries (one query whose impressions are split across two or more of the site's pages, each holding a real share — consolidate or differentiate). Rows carry clicks, impressions, CTR, position and, where it applies, expected CTR, potential clicks and the previous window's figures. Read-only.
gsc_inspect_url
ChatGPTRead Google's index status for one to 10 URLs of one Search Console property of the user's connected Google login — what the URL Inspection tool shows: the verdict (PASS, NEUTRAL, FAIL), the coverage state in Google's words (e.g. "Submitted and indexed", "Crawled - currently not indexed", "Excluded by noindex tag"), whether indexing is allowed, the robots.txt state, the page fetch state, the canonical Google chose against the one the page declares, the last crawl time and the crawler used, the sitemaps and referring pages Google found the URL through, and the rich-result verdict with any issues. Typical uses: why a page is not ranking, whether a new page is indexed yet, a canonical mismatch after a redesign. The URLs of one call are inspected in parallel. Google allows 2 000 inspections per property per day. Read-only: it never requests indexing or runs a live test.
gsc_list_sitemaps
ChatGPTList the sitemaps submitted for one Search Console property of the user's connected Google login, with each one's type, whether it is a sitemap index, when it was submitted and last downloaded by Google, whether processing is still pending, the error and warning counts Google reported, and per content type (web, image, video, news) how many URLs were submitted. Pass sitemap_url to read one sitemap alone. Typical uses: is the sitemap being fetched, did the last deploy break it, how many URLs does Google see in it. Read-only: it never submits or deletes a sitemap.
gsc_list_sites
ChatGPTList the Google Search Console properties the user's connected Google login can read — domain properties (sc-domain:example.com) and URL-prefix properties (https://example.com/) — with the login's permission level on each and whether it is verified. Call this first: every other gsc_* tool takes one of these site URLs. Read-only; reads only the user's own Search Console access.
gsc_query_search_analytics
ChatGPTReport organic Google Search performance for one Search Console property of the user's connected Google login: clicks, impressions, CTR and average position, grouped by query, page, country, device, search appearance and/or date over a date window, with filters (one landing page, non-brand queries, one country, a URL pattern) and the search surface (web, image, video, news, Discover). Typical uses: top queries, clicks by landing page, daily trend, mobile vs desktop, which queries send traffic to one URL. Rows come back one object per row keyed by the dimension names, ordered by clicks; one page per call, up to 5000 rows (default 100), pass start_row for the next page. Search Console counts organic results only — never present its clicks as paid traffic or compare them with ad clicks as like for like. Read-only.
gsc_remove_property
ChatGPTRemove one property from the Google Search Console property set of the user's connected Google login (Search Console's sites.delete). This affects only that login's access to and listing of the property — not the live website, its pages in Google Search, the property's data, or other users' access. With confirm=false (default) it reports what would be removed and changes nothing; with confirm=true — set only after the user explicitly confirmed removing that property in this conversation — it removes it.
gsc_submit_sitemap
ChatGPTSubmit or resubmit an existing sitemap URL to one Google Search Console property of the user's connected Google login (Search Console's sitemaps.submit). Use it when the user asks to submit a sitemap, or to resubmit one after fixing its errors. The connected login needs Full user or Owner permission on the property. Does not create or edit the sitemap file, does not request indexing of individual URLs, and does not guarantee Google will crawl or index the submitted pages: a success means Google accepted the submission. Check its status later with gsc_list_sitemaps.
loomascale_check_quota
ChatGPTReport the user's remaining LoomaScale allowance for the current period. On account-based plans (starter, business, portfolio) the metered unit is different ad accounts used per billing month — the answer then reports accounts used, the plan's account allowance and when it resets, and tasks are unlimited. The free trial is unlimited on both tasks and ad accounts until it ends. On the free plan of accounts from before the trial it reports tasks: used, limit, remaining and the reset date, where a task is one request in this chat — all the tool calls made to answer a single message count as one. Legacy plans are unlimited. Calling this is free — it never consumes allowance and keeps working after the quota runs out or the trial ends. This is the LoomaScale allowance only, not ad spend, ad account balance, or campaign budget.
loomascale_list_data_sources
ChatGPTLists every data source LoomaScale supports (ad platforms and Google data sources), whether each is connected to the user's LoomaScale account, and where to connect another one. Answers which other integrations are available, whether a particular platform is supported, and how to connect it. Also reports, per source, whether the plugin in use has tools for it: a source can be connected in LoomaScale and still need the full LoomaScale plugin to work with. Read-only: it starts no authorization and changes no connection. Free: it does not count against the LoomaScale allowance.
loomascale_request_feature
ChatGPTSends a feature request for an action, report or ad platform that LoomaScale does not support yet to the LoomaScale team, as a text message. Returns whether it was sent and a link to a feedback form prefilled with the same request, where the user can add details. Changes nothing in any ad account. Free: it does not count against the LoomaScale allowance.