Skip to main content
Glama
zrk-scrapers-mcp

zrk-scrapers-mcp

by Zrk1212

Bulk PageSpeed & Core Web Vitals Checker

audit_pagespeed

Run bulk PageSpeed/Lighthouse audits across many pages or whole sites to get performance, SEO, accessibility, and Core Web Vitals scores with pass/fail results and priority fixes per page.

Instructions

Run Google PageSpeed Insights / Lighthouse on many pages or whole sites. Returns performance, SEO, accessibility and best-practices scores, real-user Core Web Vitals (LCP, INP, CLS) with pass/fail, and the top fixes per page. Priced per audit. Runs the Apify actor zrk1212/pagespeed-bulk-auditor on your Apify account.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "audit_pagespeed"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsNoExact page URLs to audit.
maxItemsNoMost result rows to return in this response (default 50). The run may produce more; page with get_run_results.
strategyNoDevice to emulate (default mobile).
waitSecsNoSeconds to wait for the run to finish (default 120). If it is still running, use get_run_results later.
extraInputNoAny other input field of the Apify actor zrk1212/pagespeed-bulk-auditor, passed through as-is. See https://apify.com/zrk1212/pagespeed-bulk-auditor/input-schema
maxChargeUsdNoHard spending cap for this run in USD (default 1). Apify stops charging when it is reached.
startDomainsNoWhole websites to audit; pages are discovered from the sitemap.
fieldDataOnlyNoOnly real-user Core Web Vitals, no Lighthouse run (fast and cheap).
maxPagesPerSiteNoPages per site when using startDomains (default 25).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare a non-read-only, open-world, non-idempotent operation, and the description earns credit beyond them by disclosing the cost model ('Priced per audit') and that the run executes on the caller's own Apify account. It does not mention that waiting is time-boxed and the run may outlive the call, though the schema covers that.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: purpose first, then what is returned, then cost and execution surface. No filler, and the most decision-relevant facts (bulk scope, cost, whose account) are front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With nine optional parameters, a nested object, and no output schema, the description carries the return-value burden well by enumerating scores, Core Web Vitals with pass/fail, and top fixes per page. Remaining gaps (pagination via get_run_results, wait behavior, default cap) are handled in the schema text rather than the description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3; every parameter including the enum strategy and extraInput passthrough is documented in the schema. The description adds no parameter-level meaning such as when to prefer startDomains over urls or how maxChargeUsd interacts with the audit count.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Run Google PageSpeed Insights / Lighthouse on many pages or whole sites') and names the underlying actor, so an agent knows exactly what will execute. The bulk/site scope is stated up front, and no sibling tool in the catalog covers PageSpeed, so differentiation is implicit but unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the usage context (bulk pages or whole sites) but never states when to choose this over an alternative, when not to use it, or which mode to pick for a quick check. Guidance like using field-data-only mode for cheap real-user-only checks exists only as a schema parameter description, not in the tool description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.