Skip to main content
Glama

kadi_bence/seo-site-audit

kadi_bence--seo-site-audit
Destructive

This tool calls the Actor "kadi_bence/seo-site-audit" and retrieves its output results. Actor description: Crawl a website and score every page 0-100 for SEO with fix hints. Input: start URL(s); optional URL globs, link and image checks. Returns per page: seoScore, issues + fixes, status, redirects, title, meta, canonical, H1, broken links. Default: 20 pages. $9.50/1k pages.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "startUrls": "<startUrls>"
    },
    "name": "kadi_bence--seo-site-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxDepthNoHow many clicks away from the start URL the crawler goes, e.g. 3 for the main navigation only. 0 = only the start URL(s). Example values: 20
maxPagesNoStop after this many URLs, e.g. 500 (HTML pages, redirects and error pages all count; max 10,000). You pay only for pages that were audited successfully. Links to pages beyond the limit are still checked. Default 20. Example values: 20
waitSecsNoMax seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to poll via get-actor-run. Set to 0 to fire-and-forget.
startUrlsYes**REQUIRED** The page(s) where the crawl starts, usually your homepage, e.g. https://www.example.com/ . The crawler follows links on the same domain (www. counts as the same site). https:// is added when missing. Only audit sites you own or have permission to crawl. Example values: [{"url":"https://crawler-test.com/"}]
checkImagesNoAlso check image URLs (up to 200 per page) for 404s. Missing alt texts are always reported, even when this is off.
maxLinkChecksNoUpper limit of link targets checked that were not crawled as pages (internal links beyond Max pages, external links, images). Link checks are free, but slow servers make them take longer. Example values: 200
maxConcurrencyNoHow many pages of your site are fetched at the same time. A Crawl-delay in robots.txt always wins. Keep it low (e.g. 2-5) for small servers. Example values: 5
excludeUrlGlobsNoGlob patterns of URLs not to crawl, e.g. /tag/* or *?page=* to skip tag archives and pagination.
includeUrlGlobsNoOptional glob patterns matched against the full URL or the path, e.g. /blog/* to audit only the blog. Leave empty to crawl the whole site. Start URLs are always crawled.
includeSubdomainsNoAlso crawl subdomains, e.g. blog.example.com when you start on example.com. www. is always treated as the same site.
checkExternalLinksNoCheck links to other websites for 404s and dead domains (light HEAD requests, max 1 per second and 25 links per external site, robots.txt respected). Turn off for a faster run. Internal links are always checked. Example values: true
proxyConfigurationNoUsually not needed for your own site. If your firewall blocks the crawler, allow the user agent SEOSiteAuditBot or try the datacenter Apify Proxy. Residential proxies are not supported. Example values: {"useApifyProxy":false}
requestTimeoutSecsNoA page that does not answer in this time is reported as 'Timed out' (one retry on 429/5xx answers). Example values: 20

Output Schema

NameRequiredDescriptionDefault
tipNoAdvisory guidance RAG Web Browser wrote to its key-value store under the reserved "TIP" key
runIdYesActor run ID
statsNoRun statistics
statusYesRun status: READY | RUNNING | TIMING-OUT | TIMED-OUT | ABORTING | ABORTED | SUCCEEDED | FAILED
actorIdYesStable Apify Actor ID from the run record
summaryYesPast-tense summary of the run state
exitCodeNoActor process exit code; populated for terminal states (especially FAILED)
nextStepYesOne primary follow-up action with identifiers interpolated
storagesYesDataset and key-value store metadata, keyed by alias. "default" is always the primary entry.
actorNameNo"username/actor-name"
startedAtNoISO timestamp when the run started
finishedAtNoISO timestamp when the run finished (terminal states only)
statusMessageNoPass-through from Apify run.statusMessage
apifyConsoleUrlNoPersonalized Apify Console link to the run; present only for Console sessions

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema / properties / metaRobots / type
      Previous value: -"null"New value: +[
      +  "null",
      +  "string"
      +]
  2. Changed1 schema field changed
    • addedOutput schema / properties / storages / properties / datasets / properties / default / properties / itemsSchema
      Added value: +{
      +  "description": "JSON Schema for rows in the dataset at `storages.datasets.default.id` — describes row shape only; the rows themselves are NOT returned inline in this response. Inferred from this Actor's historical successful runs. To fetch actual rows, call `get-dataset-items` with the dataset id and a `fields` projection drawn from this schema.",
      +  "properties": {
      +    "brokenImages": {
      +      "items": {},
      +      "type": "array"
      +    },
      +    "brokenLinkCount": {
      +      "type": "number"
      +    },
      +    "brokenLinks": {
      +      "items": {
      +        "properties": {
      +          "anchor": {
      +            "type": "string"
      +          },
      +          "error": {
      +            "type": "null"
      +          },
      +          "internal": {
      +            "type": "boolean"
      +          },
      +          "status": {
      +            "type": "number"
      +          },
      +          "url": {
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "canonical": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "contentType": {
      +      "type": "string"
      +    },
      +    "crawledAt": {
      +      "type": "string"
      +    },
      +    "depth": {
      +      "type": "number"
      +    },
      +    "error": {
      +      "type": "null"
      +    },
      +    "errorCount": {
      +      "type": "number"
      +    },
      +    "externalLinks": {
      +      "type": "number"
      +    },
      +    "finalUrl": {
      +      "type": "string"
      +    },
      +    "fixes": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "foundOn": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "h1": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "h1Count": {
      +      "type": "number"
      +    },
      +    "h2Count": {
      +      "type": "number"
      +    },
      +    "hreflang": {
      +      "items": {},
      +      "type": "array"
      +    },
      +    "images": {
      +      "type": "number"
      +    },
      +    "imagesMissingAlt": {
      +      "type": "number"
      +    },
      +    "imagesMissingAltSamples": {
      +      "items": {},
      +      "type": "array"
      +    },
      +    "indexable": {
      +      "type": "boolean"
      +    },
      +    "internalLinks": {
      +      "type": "number"
      +    },
      +    "issueCount": {
      +      "type": "number"
      +    },
      +    "issues": {
      +      "items": {
      +        "properties": {
      +          "code": {
      +            "type": "string"
      +          },
      +          "message": {
      +            "type": "string"
      +          },
      +          "severity": {
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "lang": {
      +      "type": "null"
      +    },
      +    "metaDescription": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "metaDescriptionLength": {
      +      "type": "number"
      +    },
      +    "metaRobots": {
      +      "type": "null"
      +    },
      +    "nofollowLinks": {
      +      "type": "number"
      +    },
      +    "redirectChain": {
      +      "items": {},
      +      "type": "array"
      +    },
      +    "redirectCount": {
      +      "type": "number"
      +    },
      +    "responseTimeMs": {
      +      "type": "number"
      +    },
      +    "seoScore": {
      +      "type": "number"
      +    },
      +    "sizeBytes": {
      +      "type": "number"
      +    },
      +    "status": {
      +      "type": "number"
      +    },
      +    "structuredDataFormats": {
      +      "items": {},
      +      "type": "array"
      +    },
      +    "structuredDataTypes": {
      +      "items": {},
      +      "type": "array"
      +    },
      +    "title": {
      +      "type": "string"
      +    },
      +    "titleLength": {
      +      "type": "number"
      +    },
      +    "twitterCard": {
      +      "type": "null"
      +    },
      +    "url": {
      +      "type": "string"
      +    },
      +    "warningCount": {
      +      "type": "number"
      +    },
      +    "wordCount": {
      +      "type": "number"
      +    },
      +    "xRobotsTag": {
      +      "type": "null"
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already flag a non-read-only, open-world, destructive operation, so the safety profile is covered; the description adds useful economics (default 20 pages, $9.50/1k pages, pay only for successfully audited pages). However, it omits any behavior around run polling/nextStep and the waitSecs cap that materially affect how a caller experiences the tool.

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

Conciseness4/5

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

Compact three-sentence structure, front-loaded with the action and followed by returns and pricing. The boilerplate opening 'This tool calls the Actor ... and retrieves its output results' is partially redundant with the tool name and title but does not bloat the text.

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?

For a 13-parameter, nested-schema tool with an output schema, the description covers purpose, key inputs, returned fields and cost, which is enough to call it correctly. It leaves run-status polling (waitSecs/nextStep) to the schema, a minor gap but not a blocking one.

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 schema fully documents all 13 parameters, including maxDepth, glob filters, image and link checks. The description restates a few of these at a high level (start URL(s), optional URL globs, link and image checks) without adding semantics beyond the schema, so the baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource ('calls the Actor kadi_bence/seo-site-audit and retrieves its output results') and enumerates what the audit does: crawl a site, score each page 0-100 for SEO with fix hints. It does not name any sibling (e.g. pagespeed-checker or ai-readiness-audit) as an alternative, so differentiation from related audit tools is left to the reader.

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?

Gives a permission constraint ('Only audit sites you own or have permission to crawl') and a default scope of 20 pages, but never says when to choose this over the sibling audit tools or when to skip it. Usage context is implied by the SEO scoring description rather than explicitly routed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.