jd-church-website-audit

Audit a church website

audit_church_website

Audits one church homepage for mobile fit, speed, SEO basics, and first-time-guest findability, returning a report to help improve the visitor experience.

Instructions

Audits one church homepage for mobile fit, speed, SEO basics, and first-time-guest findability, and returns Journey Digital's report unchanged. Use it when the user gives one church website address. Do not use it to crawl a site, to promise a search ranking, or when no address was given. Sends that address to journeydigital.ai, which fetches the page, and the speed check to Google PageSpeed. No API key. Plugin audits store an anonymous count, so repeating the call records another count, and the church website itself is not modified. If the service is unreachable, rate-limited, or the report is malformed, the result is an error and includes no checks. Privacy: https://journeydigital.ai/privacy Terms: https://journeydigital.ai/terms

Input Schema

Name	Required	Description	Default
`url`	Yes	One church homepage, with or without https://. Not a list of pages.
`include_cta`	No	false omits the consultation note (cta). Omit this argument to keep the service default, which includes cta.

Output Schema

Name	Required	Description
`cta`	No	Consultation note. Absent when include_cta is false.
`url`	Yes	Address the service checked.
`total`	Yes	Scored checks in the service's denominator.
`checks`	Yes
`groups`	Yes
`passed`	Yes	Scored checks the service marked pass.
`couldnt`	Yes	Scored checks the service could not measure.
`js_heavy`	Yes	True when the homepage looks JavaScript-heavy.
`citations`	Yes
`final_url`	Yes	Address after redirects.
`truncated`	Yes	True when the homepage fetch hit the service's byte cap.
`disclaimer`	Yes	Disclaimer text from the service.
`speed_source`	Yes	pagespeed when Google PageSpeed returned a score, otherwise fallback.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 23, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Adds significant context beyond the annotations: data is sent to journeydigital.ai and Google PageSpeed, no API key is needed, an anonymous count is incremented on repeat calls (explaining the non-idempotent hint), the church site is not modified, and failures return an error with no checks. The privacy/terms links further disclose the data-handling surface.

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?

The core purpose and trigger are front-loaded in the first two sentences, followed by side effects and failure modes in a logical order. It is dense but nearly every sentence carries a distinct behavioral fact; the privacy/terms URLs are the only marginal additions.

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?

Given a two-parameter tool with an output schema, the description covers triggers, exclusions, external dependencies, side effects, and failure behavior. An agent has everything needed to decide to call it and interpret a failure correctly.

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 coverage is 100%, so both parameters are already fully documented in the schema (including 'one church homepage, not a list of pages'). The description reinforces the single-page scope but adds no syntax or format details beyond what the schema provides, so the baseline 3 applies.

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 ('Audits one church homepage') and enumerates the dimensions checked (mobile fit, speed, SEO basics, guest findability) plus what is returned ('Journey Digital's report unchanged'). An agent can tell exactly what this tool produces without opening the schema.

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

Usage Guidelines5/5

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

Explicit positive trigger ('when the user gives one church website address') and explicit exclusions ('Do not use it to crawl a site, to promise a search ranking, or when no address was given'). With no siblings, the exclusions do the routing work that alternatives normally would.

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

Deploy Server

Other Tools

audit_church_websiteA