site-kit

Overview Schema Source Related Servers Discussions Admin

The route from never having made a website to understanding one

learning_path

Read-only

Follow a ten-stop learning route that orders site fixes by what beginners need first, from making a site work to understanding why escape routes close. Read one stop at a time or the full path.

Instructions

Ten stops, in the order a beginner needs them — which is NOT the order the critique uses. review_site sorts by how fast a visitor notices a fault. That is right for a critique and wrong for learning. This sorts by what you need first: make it work, then make it not look broken, then make it not look generic, then make it honest, then understand why the escape routes keep closing.

Every stop is built from the rulebook itself and names the rule ids that carry its reasoning, so it cannot drift away from what the tool actually checks. Pass a stop number to read one at a time.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`stop`	No	Read one stop on its own, 1 to 10. Leave it out for the whole route.
`depth`	No	"route" is the ten stops and what to do at each. "full" (the default) adds each rule's own reasoning and the better move underneath the stop that teaches it.

Output Schema

TableJSON Schema

Name	Required	Description
`fix`	No
`why`	No
`tool`	Yes	Which tool produced this.
`stops`	No
`status`	Yes	pass = checked and clean. fail = checked and found problems. skipped = nothing was measured. error = the tool could not run.
`problem`	No
`headline`	Yes	One sentence verdict, safe to show a non-technical user.
`error_code`	No	Set only when status is "error".
`rules_total`	No
`rules_uncovered`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Sep 17, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already mark this as read-only, and the description adds useful behavioral context: stops are derived from the rulebook, cite rule ids, and are deliberately ordered for learning rather than fault detection. This goes beyond the safety hints and clarifies what the agent can expect from the content.

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?

The description is compact yet information-dense, with every sentence serving a purpose: defining the route, distinguishing it from review_site, explaining provenance, and giving usage guidance. It front-loads the core concept and avoids filler.

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?

With an output schema present, a read-only annotation, and only two optional parameters fully documented in the schema, the description supplies all necessary context for correct use. It explains the ordering rationale, the relationship to review_site, and the stop-by-stop access pattern.

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 parameters are already well documented. The description adds a small clarification about passing a stop number, but it does not meaningfully extend the schema's explanation of the depth parameter.

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?

The description explicitly defines the tool as a ten-stop learning path ordered by what a beginner needs first, and differentiates it from review_site's critique-oriented order. This gives a clear verb-resource relationship and makes sibling distinction immediate.

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?

It explicitly contrasts with review_site, stating that review_site's ordering is right for a critique and wrong for learning, which tells the agent when to use this tool versus that sibling. It also gives a direct usage instruction: pass a stop number to read one stop at a time.

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

Deploy Server