context_profile_build
Build the bounded public site-profile facts: robots.txt, at most 3 sitemap documents and at most 10 selected pages per run, fetched on the verifier’s public fetch boundary with the CLI’s courtesy pacing, with every limit the run hit reported as a count. Facts keep derived fields (titles, h1s, description, canonical, link counts, sitemap membership, byte hashes, fetched_at), never raw HTML. A page that could not be read is unknown/unreadable, never “no assets”, and missing pages stay explicit.
Repository-local stdio MCP only. This tool is absent from hosted MCP and HTTP. It can write local context files or fetch bounded public context.
Setup and request
Start the local context host with an explicit repository root. Paths are restricted to that root, including symlink resolution.Input fields
Returned result
Captured from a local fixture repository without external credentials.Full response example
Full response example
state(string, required): Profile build completed; individual pages may remain unreadable.origin(string, required): Resolved public site origin.built_at(string, required): Run start timestamp.robots(object, required): Robots document outcome.sitemaps(object, required): Bounded sitemap discovery.pages(array, required): Bounded selected-page outcomes.limits(object, required): Applied limits and actual selection.rows_written(integer, required): Fact rows appended; includes robots, sitemaps and pages.notes(array, required): Explicit cap and unreadable-page notes.
All fields and nested objects
All fields and nested objects
Types, allowed values, limits and nested fields:
Result and recovery
The host returns JSON in bothstructuredContent and text content. The local context reference describes each result, file ownership and recovery. Start/end dates must be supplied together. Thrown input or file failures return isError: true. Missing manual/profile files and unresolved citations also flag an error. Inspect returned connection states separately: revoked or unavailable access can be result data. Manual-only configuration is valid.
See local context, CLI context commands and schema conventions.