Resolve a date range
Turn a named range like last_7_days or last_month into concrete start/end dates (YYYY-MM-DD) in a timezone. Feed the result into analytics report operations.
util_date_range- Safety
- Read-only
- Plan
- Free
A transparent view of what this integration exposes now, what it costs, which plan it needs, and where a human approval is required.
Updated 1 August 2026 from the public registry.
These rows are projected from the same registry used by the API, workflows, agent, and MCP surfaces. Private or disabled operations cannot appear here.
Turn a named range like last_7_days or last_month into concrete start/end dates (YYYY-MM-DD) in a timezone. Feed the result into analytics report operations.
util_date_rangeReturn the first (or last) N items of a list. Use to cap an upstream list before an expensive per-item operation.
util_takeExplore the complete executable definition before connecting a workspace.
Sample a site's sitemap, audit each selected page, aggregate repeated technical failures, and produce a crawl-efficiency priority map focused on indexability, canonical consistency, redirects, thin pages, and repeated template-level defects. A guard step stops the run if the URL is a sitemap index, so point the workflow at a child sitemap that lists page URLs directly.
web_get_sitemapconditionutil_takeweb_audit_pageweb_audit_summaryai_analyze_datareport_renderSample a site's priority inventory, audit technical SEO, conversion, and AI-visibility signals, aggregate recurring issues, and render an executive scorecard that translates page-level evidence into business risk, decisions, owners, and a focused next-month agenda. A guard step stops the run if the URL is a sitemap index, so point the workflow at a child sitemap that lists page URLs directly.
web_get_sitemapconditionutil_takeweb_audit_pageweb_audit_summaryai_analyze_datareport_renderCollect separate GA4 campaign and landing-page views for the current period and produce a cautious investigation brief without pretending the two reports form a row-level causal join.
ga4_select_accountsutil_date_rangega4_get_reportga4_get_reportai_analyze_datareport_renderRun three bounded GA4 acquisition breakdowns to review campaign naming, source and medium coverage, engagement, key events, and revenue. The final brief distinguishes tracking-hygiene findings from performance observations and does not assign a synthetic campaign quality score.
ga4_select_accountsutil_date_rangega4_get_reportai_analyze_datareport_renderReview current-period GA4 channel-group rows for observed traffic, engagement, key-event, and revenue patterns, then produce a measurement-safe quality brief without assigning channel causation.
ga4_select_accountsutil_date_rangega4_get_reportai_analyze_datareport_renderReview current-period GA4 country aggregates for observed traffic, engagement, key events, and revenue signals, then create localization questions without treating country as a causal or market-fit conclusion.
ga4_select_accountsutil_date_rangega4_get_reportai_analyze_datareport_renderReview current-period GA4 device-category aggregates for sessions, engagement, key events, and revenue, then create a responsive and instrumentation follow-up brief without device causation claims.
ga4_select_accountsutil_date_rangega4_get_reportai_analyze_datareport_renderReview current-period GA4 event-name aggregates for volume, engagement, key-event, and revenue signals, then identify event taxonomy and instrumentation checks without certifying tracking quality.
ga4_select_accountsutil_date_rangega4_get_reportai_analyze_datareport_renderRead daily GA4 engagement signals across the last 28 complete days and turn them into a compact trend brief. The analysis separates sustained movement from isolated daily variation, reports exact observed values, and avoids unsupported explanations for changes.
ga4_select_accountsutil_date_rangega4_get_reportai_analyze_datareport_renderReview a bounded set of GA4 landing-page rows for high-traffic pages with weak engagement or conversion signals, then create an investigation brief. Results are diagnostic candidates from observed analytics data, not proof that a page caused lost key events or revenue.
ga4_select_accountsutil_date_rangega4_get_reportconditionai_analyze_datareport_renderReview a bounded GA4 landing-page report for observed traffic, engagement, key-event, and revenue signals, then produce a measurement-safe page investigation brief without assigning lost value or causal blame.
ga4_select_accountsutil_date_rangega4_get_reportai_analyze_datareport_renderReview current-period GA4 page-path rows for sessions, key events, and recorded revenue, then produce a verification brief that avoids assigning revenue causation to pages.
ga4_select_accountsutil_date_rangega4_get_reportai_analyze_datareport_renderReview current-period GA4 source and medium rows for naming hygiene, engagement, key-event, and revenue signals, keeping observed analytics separate from attribution claims.
ga4_select_accountsutil_date_rangega4_get_reportai_analyze_datareport_renderSample pages from a sitemap, audit their title, meta description, canonical, robots, H1, language, Open Graph, and structured-data signals, then produce a remediation inventory organized by repeated template defect and search-snippet risk. A guard step stops the run if the URL is a sitemap index, so point the workflow at a child sitemap that lists page URLs directly.
web_get_sitemapconditionutil_takeweb_audit_pageai_analyze_datareport_renderPlace GA4 Organic Search rows beside daily Search Console performance for the same 28-day window and produce an executive scorecard. The workflow highlights directional patterns while keeping platform definitions separate and refusing to present correlation as attribution.
ga4_select_accountsgsc_select_accountsutil_date_rangega4_get_reportgsc_get_reportai_analyze_datareport_renderUse explicit brand terms to produce a model-assisted narrative grouping of a bounded Search Console query sample. The report keeps ambiguous examples visible and does not claim exhaustive classification, row preservation, total demand coverage, or market share.
gsc_select_accountsutil_date_rangegsc_get_reportai_analyze_datareport_renderReview a bounded Search Console country-device aggregate to surface observed market and responsive-search questions while keeping sparse combinations, omitted rows, and causation explicit.
gsc_select_accountsutil_date_rangegsc_get_reportai_analyze_datareport_renderCombine country-level and country-by-query Search Console views into a geographic demand brief for the returned sample. Country keys and metrics are preserved as reported, while the analysis avoids market-size estimates, location intent assumptions, and unsupported expansion claims.
gsc_select_accountsutil_date_rangegsc_get_reportgsc_get_reportai_analyze_datareport_renderReview current-period Search Console country aggregates to identify where search demand is observed and which localization or market checks deserve validation, without treating volume as revenue or market causation.
gsc_select_accountsutil_date_rangegsc_get_reportai_analyze_datareport_renderSummarize current-period Search Console device rows and surface observed click, impression, CTR, and position differences for a responsive-search review without claiming a device caused performance changes.
gsc_select_accountsutil_date_rangegsc_get_reportai_analyze_datareport_renderCompare Search Console performance first by device and then by device plus query to find returned queries whose clicks, CTR, or position differ materially across device categories. The workflow treats those differences as investigation opportunities, not proof of a device-specific experience problem.
gsc_select_accountsutil_date_rangegsc_get_reportai_analyze_datareport_renderReview current-period Search Console page aggregates to identify pages with observed clicks, impressions, CTR, and position signals that deserve indexing and content verification.
gsc_select_accountsutil_date_rangegsc_get_reportai_analyze_datareport_renderReview a bounded Search Console page and query sample to identify observed intent clusters and pages worth investigation, while keeping query evidence, page evidence, and omitted rows explicit.
gsc_select_accountsutil_date_rangegsc_get_reportai_analyze_datareport_renderReview a bounded current-period Search Console page sample and surface pages with weak CTR, attainable average positions, or meaningful click demand worth protecting. This snapshot does not measure decay or sustained deterioration because it does not query a comparable prior period, and it does not represent every indexed page.
gsc_select_accountsutil_date_rangegsc_get_reportconditionai_analyze_datareport_renderReview current-period Search Console page and search-appearance aggregates to identify pages and features needing markup or snippet validation without claiming eligibility or complete visibility.
gsc_select_accountsutil_date_rangegsc_get_reportai_analyze_datareport_renderReview current-period Search Console query aggregates for impression, click, CTR, and position opportunities, with explicit sample limits and no unsupported momentum or ranking claims.
gsc_select_accountsutil_date_rangegsc_get_reportai_analyze_datareport_renderReview a bounded current-period Search Console query sample and surface high-impression, weak-CTR, and attainable-position opportunities for investigation. This snapshot does not measure momentum, decline, or newly visible demand because it does not query a comparable prior period, and omitted rows remain unknown.
gsc_select_accountsutil_date_rangegsc_get_reportconditionai_analyze_datareport_renderReview current-period Search Console search-appearance aggregates to surface observed rich-result and feature visibility questions, with exact evidence and clear limits around coverage, eligibility, and causation.
gsc_select_accountsutil_date_rangegsc_get_reportai_analyze_datareport_renderFetch your sitemap, run an on-page technical-SEO audit of a sample of its pages (title, meta description, canonical, indexability, H1s, mobile viewport, image alt coverage, content length, Open Graph — scored 0–100), aggregate the sampled pages into one scorecard, and have the AI write a prioritized action plan. A guard step stops the run if the URL is a sitemap index, so point the workflow at a child sitemap that lists page URLs directly.
web_get_sitemapconditionutil_takeweb_audit_pageweb_audit_summaryai_analyze_dataFetch your sitemap, run an on-page technical-SEO audit of a sample of its pages (title, meta description, canonical, indexability, H1s, mobile viewport, image alt coverage, content length, Open Graph — scored 0–100), aggregate the sampled pages into a scorecard, have the AI write a prioritized action plan, and render it all into a branded HTML report saved to Files (open it and print to PDF, or attach it to a client). A guard step stops the run if the URL is a sitemap index, so point the workflow at a child sitemap that lists page URLs directly. This is the reporting workflow MarkMate runs on itself.
web_get_sitemapconditionutil_takeweb_audit_pageweb_audit_summaryai_analyze_datareport_renderAn autopilot rule: audit a fixed sample of pages from your sitemap on a schedule, and when the sample's average SEO score drops below your threshold, send an alert webhook (Slack/Discord/Zapier) — after you approve it. A guard step stops the run if the URL is a sitemap index, so point the workflow at a child sitemap that lists page URLs directly. The alert step is a write, so it always pauses in the approval inbox; if the score is healthy, the run ends quietly.
web_get_sitemapconditionutil_takeweb_audit_pageweb_audit_summaryconditionweb_post_webhookTake a bounded sample from a direct URL-set sitemap, probe each URL, and preserve status, redirect, and failure evidence in a report.
web_get_sitemapconditionutil_takeweb_check_url_statusreport_renderSample page URLs from a URL-set sitemap, fetch bounded text, and review visible language, titles, headings, and content consistency without claiming complete localization or content quality coverage.
web_get_sitemapconditionutil_takeweb_fetch_pageai_analyze_datareport_renderRead the titles and bounded text snapshots for a sample of sitemap URLs, then save the evidence for editorial and technical review.
web_get_sitemapconditionutil_takeweb_fetch_pagereport_renderRead a bounded sitemap page sample, ask the configured AI model to organize observable content themes and review questions, and save the source sample with the advisory brief.
web_get_sitemapconditionutil_takeweb_fetch_pageai_analyze_datareport_renderFetch a bounded sample of pages from a URL-set sitemap and review titles, visible text, headings, and readability signals while preserving the difference between sampled evidence and a complete editorial audit.
web_get_sitemapconditionutil_takeweb_fetch_pageai_analyze_datareport_renderRead a URL-set sitemap, sample its newest entries, check their HTTP status, and produce a bounded freshness-risk brief. It reports current responses only and does not infer publication dates or full sitemap coverage.
web_get_sitemapconditionutil_takeweb_check_url_statusai_analyze_datareport_renderSample URLs from a child sitemap, probe their final HTTP destinations, and store a bounded redirect and availability report. This is useful during releases and migrations without pretending to measure every redirect hop.
web_get_sitemaputil_takeweb_check_url_statusreport_renderSample a URL-set sitemap and check redirect behavior for a bounded set of pages, producing a release-oriented report that keeps HTTP evidence separate from canonical and SEO conclusions.
web_get_sitemapconditionutil_takeweb_check_url_statusai_analyze_datareport_renderSample direct sitemap URLs, inspect their final destinations, and save redirect evidence alongside the sample scope for technical SEO review.
web_get_sitemapconditionutil_takeweb_check_url_statusreport_renderRead a production sitemap, sample a configurable slice of its URLs, verify that they resolve successfully, and create a release-oriented report covering missing inventory, accidental redirects, and pages that need immediate search visibility review. A guard step stops the run if the URL is a sitemap index, so point the guard at the child sitemap for the released surface.
web_get_sitemapconditionutil_takeweb_check_url_statusai_analyze_datareport_renderAudit a bounded sample of sitemap pages, aggregate technical checks into a scorecard, and save a reviewable report without generating a causal or ranking claim.
web_get_sitemapconditionutil_takeweb_audit_pageweb_audit_summaryreport_renderTake one bounded sitemap sample, inspect both URL status and page content, and preserve the two evidence streams together for release review.
web_get_sitemapconditionutil_takeweb_check_url_statusweb_fetch_pagereport_renderSample pages from a URL-set sitemap, inspect their on-page structured-data signals, and produce a cautious AI review of schema coverage and validation follow-ups.
web_get_sitemapconditionutil_takeweb_audit_pageai_analyze_datareport_renderCheck a bounded tail sample from a URL-set sitemap and create a direct availability watch report for recently listed entries, without interpreting sitemap order as publication time.
web_get_sitemapconditionutil_takeweb_check_url_statusai_analyze_datareport_renderSample a URL-set sitemap, run bounded on-page technical audits, aggregate findings, and render a site audit artifact with explicit sample limits and no synthetic full-site score.
web_get_sitemapconditionutil_takeweb_audit_pageweb_audit_summaryreport_renderAudit a bounded sitemap sample, aggregate technical findings, and save a repeatable triage report with sample limits and the measured scorecard.
web_get_sitemapconditionutil_takeweb_audit_pageweb_audit_summaryreport_renderRead a URL-set sitemap, guard against sitemap indexes, check a bounded set of listed URLs, and render direct HTTP status and redirect evidence without claiming full-site uptime.
web_get_sitemapconditionutil_takeweb_check_url_statusreport_renderCompare bounded GA4 landing-page traffic rows with Search Console page visibility for the same period, then surface page-level mismatches worth checking. The workflow explicitly treats GA4 sessions and Search Console clicks as different measurements and does not manufacture a cross-platform attribution model.
ga4_select_accountsgsc_select_accountsutil_date_rangega4_get_reportgsc_get_reportconditionconditionai_analyze_datareport_renderCollect separate GA4 channel, source-medium, and campaign views plus a bounded Search Console query-page view for the last seven complete days. The final report summarizes acquisition mix and search demand while keeping channel performance, search visibility, and attribution claims distinct.
ga4_select_accountsgsc_select_accountsutil_date_rangega4_get_reportga4_get_reportga4_get_reportgsc_get_reportai_analyze_datareport_renderCompare the operating model or open a workspace and start with a visible requirement check.