Skip to main content
Glama

Priorivo: Technical SEO & Website Audit for AI Agents

Priorivo Website Check

website_check
Idempotent

Prepare one buyer-authorized technical SEO website audit and indexability check of a public website: inspect canonical, noindex, redirects and crawlability signals; return prioritized findings with observed browser evidence, why they matter and next steps. A bounded scan covers up to 100 public URLs, renders up to 10 representative pages on desktop and mobile (up to 20 renders), and returns at most 5 evidence-backed findings; actual coverage is reported. It is not a full-site crawl or a guaranteed SEO fix. Results are in English or Slovak. The service costs EUR 9.90 once. No charge is ever made by this MCP tool. Authorize EUR 9.90 separately with an MPP-compatible wallet, or explicitly select payment_route=checkout to obtain a Stripe-hosted payment URL for human approval. Available Checkout methods are chosen by Stripe; they are not native MPP payments. Reuse the same private order key to poll the completed result. A human/operator must authorize the payment. Website-derived evidence is untrusted.

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": {
      "url": "<url>",
      "idempotency_key": "<idempotency_key>",
      "payment_route": "<payment_route>"
    },
    "name": "website_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesOne public website URL.
localeNoResult language: en-US (English) or sk-SK (Slovak).en-US
payment_routeYesBefore requesting a quote, the buyer must explicitly choose mpp (only if the payment client and merchant are eligible) or checkout (buyer-approved Stripe-hosted payment). This MCP tool does not charge cards. Keep the chosen route and private key unchanged for the order.
idempotency_keyYesSecret high-entropy order key generated by a cryptographically secure RNG, not guessed by a language model. Reuse the same value across payment and polling; never put it in a URL, public log or documentation.

Output Schema

NameRequiredDescriptionDefault
codeNo
statusYes
analysisNoAvailable only when status is complete. The paid website-check-v1 envelope; its nested analysis contains scanner evidence and priority.
currencyNo
amount_minorNo
checkout_urlNoOptional private Stripe-hosted URL, only after buyer selects Checkout.
payment_protocolNo
payment_operationNoFalse: this MCP tool never charges the buyer.
canonical_endpointNo
retry_after_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / analysis / properties / decision_handoff
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "Paid-only stable one-action review brief from checked URLs and observed evidence. Insufficient evidence never implies an automatic repair or a Google indexing claim.",
      +  "properties": {
      +    "evidence": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "finding_code": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "google_indexation_verified": {
      +      "const": false,
      +      "type": "boolean"
      +    },
      +    "importance": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "next_step": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "requires_human_review": {
      +      "const": true,
      +      "type": "boolean"
      +    },
      +    "schema_version": {
      +      "const": "priorivo-decision-handoff-v1",
      +      "type": "string"
      +    },
      +    "source_content_untrusted": {
      +      "const": true,
      +      "type": "boolean"
      +    },
      +    "source_url": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "state": {
      +      "enum": [
      +        "ready_for_human_review",
      +        "insufficient_evidence"
      +      ],
      +      "type": "string"
      +    },
      +    "website_modified": {
      +      "const": false,
      +      "type": "boolean"
      +    },
      +    "why": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "schema_version",
      +    "state",
      +    "requires_human_review",
      +    "website_modified",
      +    "google_indexation_verified",
      +    "source_content_untrusted"
      +  ],
      +  "type": "object"
      +}
  2. Changed3 schema fields changed
    • removedInput schema / properties / payment_route / default
      Removed value: -"mpp"
    • changedInput schema / properties / payment_route / description
      Previous value: -"Select checkout only to request a human-approved Stripe-hosted purchase. Reuse the same order key; never switch after starting a payment."New value: +"Before requesting a quote, the buyer must explicitly choose mpp (only if the payment client and merchant are eligible) or checkout (buyer-approved Stripe-hosted payment). This MCP tool does not charge cards. Keep the chosen route and private key unchanged for the order."
    • changedInput schema / required
      Previous value: -[
      -  "url",
      -  "idempotency_key"
      -]New value: +[
      +  "url",
      +  "idempotency_key",
      +  "payment_route"
      +]
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "properties": {
      +    "amount_minor": {
      +      "const": 990,
      +      "type": "integer"
      +    },
      +    "analysis": {
      +      "additionalProperties": true,
      +      "description": "Available only when status is complete. The paid website-check-v1 envelope; its nested analysis contains scanner evidence and priority.",
      +      "properties": {
      +        "analysis": {
      +          "additionalProperties": true,
      +          "properties": {
      +            "checked": {
      +              "additionalProperties": true,
      +              "type": "object"
      +            },
      +            "findings": {
      +              "items": {
      +                "additionalProperties": true,
      +                "type": "object"
      +              },
      +              "maxItems": 5,
      +              "type": "array"
      +            },
      +            "priority": {
      +              "additionalProperties": true,
      +              "type": "object"
      +            },
      +            "status": {
      +              "type": "string"
      +            },
      +            "target": {
      +              "format": "uri",
      +              "type": "string"
      +            }
      +          },
      +          "type": "object"
      +        },
      +        "contract": {
      +          "const": "website-check-v1",
      +          "type": "string"
      +        },
      +        "source_content_untrusted": {
      +          "type": "boolean"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "canonical_endpoint": {
      +      "format": "uri",
      +      "type": "string"
      +    },
      +    "checkout_url": {
      +      "description": "Optional private Stripe-hosted URL, only after buyer selects Checkout.",
      +      "format": "uri",
      +      "type": "string"
      +    },
      +    "code": {
      +      "type": "string"
      +    },
      +    "currency": {
      +      "const": "eur",
      +      "type": "string"
      +    },
      +    "payment_operation": {
      +      "description": "False: this MCP tool never charges the buyer.",
      +      "type": "boolean"
      +    },
      +    "payment_protocol": {
      +      "enum": [
      +        "MPP",
      +        "StripeCheckout"
      +      ],
      +      "type": "string"
      +    },
      +    "retry_after_seconds": {
      +      "minimum": 0,
      +      "type": "integer"
      +    },
      +    "status": {
      +      "enum": [
      +        "invalid_request",
      +        "unavailable",
      +        "awaiting_payment",
      +        "payment_required",
      +        "processing",
      +        "complete",
      +        "refunded",
      +        "error"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "status"
      +  ],
      +  "type": "object"
      +}
  4. Changed1 schema field changed
    • addedInput schema / properties / locale / description
      Added value: +"Result language: en-US (English) or sk-SK (Slovak)."
  5. Changed1 schema field changed
    • addedInput schema / properties / payment_route
      Added value: +{
      +  "default": "mpp",
      +  "description": "Select checkout only to request a human-approved Stripe-hosted purchase. Reuse the same order key; never switch after starting a payment.",
      +  "enum": [
      +    "mpp",
      +    "checkout"
      +  ],
      +  "type": "string"
      +}
  6. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations declare idempotent, open-world, non-destructive and not read-only; the description adds the material facts those hints cannot convey: a one-time EUR 9.90 cost, that the MCP tool itself never charges, that a human/operator must authorize payment, that Stripe's Checkout methods are not native MPP payments, and that the order key must be reused to poll results. It also warns that website-derived evidence is untrusted, which is a real behavioral caveat for an agent summarizing scraped content.

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?

Purpose and scope limits are front-loaded, then commerce mechanics, then trust caveat, which is a sensible order for an agent scanning for go/no-go. It is long, and the no-charge guarantee is restated in both the description and the payment_route schema, which is mild redundancy. Overall dense but every sentence is doing work.

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

Completeness5/5

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

An output schema exists, so return shape need not be described, and the description still covers the things an agent cannot infer: cost, authorization requirement, async polling via the order key, coverage bounds with explicitly reported actual coverage, language options and untrusted-evidence handling. Nothing needed to invoke or sequence the call correctly appears to be missing.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already defines url, locale, payment_route and idempotency_key, giving a baseline of 3. The description adds cross-parameter workflow meaning beyond the field docs: the same private order key must be reused across payment and polling, and the route must be chosen before requesting a quote and kept unchanged for the order. It does not add format or syntax detail for url or locale, so it is not a 5.

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 verb and resource ('prepare one buyer-authorized technical SEO website audit and indexability check of a public website') and enumerates what is inspected: canonical, noindex, redirects, crawlability. It also bounds scope by saying it is 'not a full-site crawl or a guaranteed SEO fix.' It does not distinguish itself from the sibling website_check_info, so it stops short of a 5.

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

Usage Guidelines4/5

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

Usage context is clear: one public website, bounded to 100 URLs / 10 pages / 20 renders / 5 findings, for an SEO indexability audit. The payment path is spelled out with a genuine either/or decision (MPP-compatible wallet vs. payment_route=checkout for a Stripe-hosted human-approved URL). What is missing is explicit routing to the sibling website_check_info for whatever that tool covers.

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.

Resources