Skip to main content
Glama

kadi_bence/ai-readiness-audit

kadi_bence--ai-readiness-audit
Destructive

This tool calls the Actor "kadi_bence/ai-readiness-audit" and retrieves its output results. Actor description: Score websites 0-100 for AI search (GEO/AEO). Input: websites or page URLs. Returns per site: score, grade, fix list, access map for 20 AI crawlers (GPTBot, ClaudeBot, PerplexityBot), llms.txt check and draft, JSON-LD, raw-HTML content. No API key. $8/1k sites.

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": "kadi_bence--ai-readiness-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsNoOne per line, e.g. example.com or https://example.com/pricing. Each one is audited: its robots.txt, llms.txt and sitemap, plus that page. Example values: ["apify.com","https://www.anthropic.com"]
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.
generateLlmsTxtNoFor sites without an llms.txt, adds a ready-to-edit draft built from the page title, description and internal links. Example values: true
proxyConfigurationNoUsually not needed. If a site blocks the Actor, try the datacenter Apify Proxy. Residential proxies are not supported. Example values: {"useApifyProxy":false}

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
    • 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": {
      +    "aiCrawlers": {
      +      "items": {
      +        "properties": {
      +          "allowed": {
      +            "type": "boolean"
      +          },
      +          "crawler": {
      +            "type": "string"
      +          },
      +          "owner": {
      +            "type": "string"
      +          },
      +          "purpose": {
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "aiReadinessScore": {
      +      "type": "number"
      +    },
      +    "blockedAnswerCrawlers": {
      +      "items": {},
      +      "type": "array"
      +    },
      +    "canonical": {
      +      "type": "string"
      +    },
      +    "checkedAt": {
      +      "type": "string"
      +    },
      +    "error": {
      +      "type": "null"
      +    },
      +    "errorCount": {
      +      "type": "number"
      +    },
      +    "finalUrl": {
      +      "type": "string"
      +    },
      +    "grade": {
      +      "type": "string"
      +    },
      +    "h1": {
      +      "type": "string"
      +    },
      +    "hasDate": {
      +      "type": "boolean"
      +    },
      +    "issues": {
      +      "items": {
      +        "properties": {
      +          "check": {
      +            "type": "string"
      +          },
      +          "fix": {
      +            "type": "string"
      +          },
      +          "message": {
      +            "type": "string"
      +          },
      +          "severity": {
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "jsonLdBroken": {
      +      "type": "number"
      +    },
      +    "jsonLdTypes": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "language": {
      +      "type": "string"
      +    },
      +    "listsAndTables": {
      +      "type": "number"
      +    },
      +    "llmsTxt": {
      +      "properties": {
      +        "found": {
      +          "type": "boolean"
      +        },
      +        "fullVersionFound": {
      +          "type": "boolean"
      +        },
      +        "linkCount": {
      +          "type": "number"
      +        },
      +        "problems": {
      +          "items": {},
      +          "type": "array"
      +        },
      +        "url": {
      +          "type": "string"
      +        },
      +        "valid": {
      +          "type": "boolean"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "llmsTxtDraft": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "metaDescription": {
      +      "type": "string"
      +    },
      +    "metaRobots": {
      +      "type": [
      +        "null",
      +        "string"
      +      ]
      +    },
      +    "noindex": {
      +      "type": "boolean"
      +    },
      +    "ogTitle": {
      +      "type": "string"
      +    },
      +    "questionHeadings": {
      +      "type": "number"
      +    },
      +    "robotsTxtFound": {
      +      "type": "boolean"
      +    },
      +    "scoreBreakdown": {
      +      "properties": {
      +        "answerStructure": {
      +          "type": "number"
      +        },
      +        "crawlerAccess": {
      +          "type": "number"
      +        },
      +        "llmsTxt": {
      +          "type": "number"
      +        },
      +        "metadata": {
      +          "type": "number"
      +        },
      +        "renderedContent": {
      +          "type": "number"
      +        },
      +        "sitemap": {
      +          "type": "number"
      +        },
      +        "structuredData": {
      +          "type": "number"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "sitemapFound": {
      +      "type": "boolean"
      +    },
      +    "status": {
      +      "type": "number"
      +    },
      +    "subheadingCount": {
      +      "type": "number"
      +    },
      +    "title": {
      +      "type": "string"
      +    },
      +    "url": {
      +      "type": "string"
      +    },
      +    "warningCount": {
      +      "type": "number"
      +    },
      +    "wordCount": {
      +      "type": "number"
      +    }
      +  },
      +  "type": "object"
      +}
  2. 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 openWorldHint and destructiveHint, so the description could have added useful context about side effects, and it does add real value with 'No API key' and '$8/1k sites' pricing. However, it says nothing about run latency, the fact that the call may return before completion (the waitSecs cap and follow-up polling behavior documented only in the schema), or what happens when a site blocks scraping. Given destructiveHint=true, the absence of any caveat about the operation is a notable gap.

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?

Two compact sentences with the capability and the return payload front-loaded, followed by cost and access constraints. The opening boilerplate ('This tool calls the Actor ... and retrieves its output results') is mild filler that a reader could skip, but nothing is bloated or buried.

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 an output schema present, the description needn't enumerate return values, yet it helpfully summarizes them; combined with full schema coverage on all four parameters, the agent has enough to invoke correctly. The remaining gap is the asynchronous run/polling behavior for long audits, which is only discoverable in the waitSecs schema text.

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 parameter layer is already fully documented, including waitSecs' 0-45 cap and the proxy guidance. The description only reiterates the URL input, adding nothing about waitSecs, generateLlmsTxt, or proxyConfiguration. Baseline 3 applies since the schema does the heavy lifting.

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?

The description names a specific resource and action: it runs the 'kadi_bence/ai-readiness-audit' Actor and returns its results, then explains the Actor scores websites 0-100 for AI search readiness (GEO/AEO). An agent knows exactly what comes back (score, grade, fix list, crawler access map, llms.txt draft, JSON-LD). It does not, however, distinguish this from the sibling 'ai-visibility-tracker', which sounds like an adjacent capability.

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?

Usage is only implicit: 'Input: websites or page URLs' tells the agent the tool takes site URLs, but there is no explicit statement of when to choose this over the visibility tracker, nor when not to use it. No prerequisites or failure conditions are described beyond 'No API key.' The agent must infer the use case from the purpose sentence.

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.