Rewrite for Answer Engine Optimization
rewrite_aeoRewrite content to optimize for AI answer engines like ChatGPT, Perplexity, and Google AI Overviews. Add BLUF opening, FAQ structure, and schema markup based on the target query.
Instructions
Rewrite a content block for Answer Engine Optimization. Adds a BLUF opening, FAQ structure, schema additions, and concise question-shaped headings tuned for ChatGPT / Perplexity / Google AI Overviews.
Read-only when given url (one HTTP GET). Zero network when given text. The tool does NOT write back to the URL - it only returns the rewritten content as a string. No side effects on the source.
This tool delegates the actual rewrite to the calling LLM via MCP sampling - it does not call any external API itself. The MCP host's model produces the rewrite. Same input may produce different output across runs (model-dependent).
When to use: optimizing content for direct-answer surfaces (definitions, how-tos, FAQs). For Generative Engine Optimization (entity-rich, comparison-ready synthesis), use rewrite_geo instead.
Either url or text must be provided. target_query is required.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | Public URL whose content should be fetched and rewritten. Either this OR `text` is required. | |
| text | No | Raw content (markdown or HTML) to rewrite directly. Either this OR `url` is required. | |
| format | No | Output shape. `article` for prose-with-headings. `faq` for Q&A list. `howto` for numbered-step procedural content with HowTo schema hints. `comparison` for X-vs-Y tables. Default `article`. | article |
| max_words | No | Soft word budget for the rewrite. Default 1500. Range 100-5000. The rewrite tries to stay under this; very small budgets may force truncation. | |
| target_query | Yes | The user query the rewrite should answer (e.g. `what is RAG`, `how to deploy Ghost to Docker`). Required - drives heading shape and BLUF wording. | |
| respect_robots | No | If true (default), respect robots.txt when fetching `url`. Ignored when `text` is used. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | ||
| notes | Yes | Notes from the rewrite (e.g. truncations, format adjustments). | |
| format | No | Output format (article, faq, howto, comparison). | |
| source | Yes | ||
| rewritten | Yes | The rewritten content. The caller decides where to publish it. | |
| target_query | Yes |