preview_page

com.pagefully/mcp · Verify this server

One page, whole: each screenshot with its headline, subline and picture, the promotional text, the keywords it is for, what pre-flight found, whether it is approved, and its preview_url on pagefully.com. The screenshots also come back as images (display size, at most six) where the client can show them, and a chat app that draws MCP Apps shows the page inline as the App Store would, with buttons to open the full preview, approve, and ask for a headline change. Call it when a page's job is done, and again after an edit. Always give the person the preview_url: a page is something they look at before they say yes, and the web preview is the full-size view. Tell them what pre-flight failed or warned about. While preflight.blocked is true the page cannot be approved or published: fix what is marked with edit_page. Each finding names the words it is about ("text"), the rule ("rule": its name, and what counts as breaking it) and how it was decided ("source"). A rule that matched exact words gives them in "phrase". A judgement is the classifier reading the whole line: "probability" is how likely the line breaks the rule and "phrase" is null, so reword the line and do not guess at a phrase. A warning does not block: it is for the person to look at. Each screenshot has "design" (ours, theirs or kept) and "own_words". own_words true means the picture still shows the developer's own words and the headline in the answer is not on it. The pictures here are a page's screenshots after rewording. The app's own source screens are in analyze_app, under "screens".