Today WP

Use when you need the official page for a function, hook, class, block API, REST route, WP-CLI command or common task (nonces, cron, roles, caching...), or a page builder's developer docs: returns the right links with a one-line summary, not the page content. For a step-by-step walkthrough, use wp_howto.

Use when Today WP itself got something wrong: an answer, page or fact that looked wrong, outdated, missing or confusing, or an idea. One short note. To rate a plugin or doc, use wp_report. category: wrong (A fact that is not true.), outdated (True once, not anymore.), missing (Something an agent needed and did not get.), confusing (Hard to act on, ambiguous or misleading.), broken (A tool error, a dead link, a timeout.), idea (Something that would make answers better.). about: one of "A tool answer", "A plugin or page builder", "A doc or guide", "A news item", "This site", "Today WP itself". Never include the site address, prompts or code.

Use when the user wants step-by-step help with a common task (connecting AI and MCP, images and media, speed and database, SEO, security, fixing errors): returns links to hands-on guides with a short summary. For an API or function reference, use wp_docs.

Use when the user asks what is new in WordPress, or a recent release or announcement may matter to the task: the latest articles from official WordPress blogs, news sites, security researchers and makers, newest first, with source, date, summary and link. For what changed and what to do in code, use wp_now.

Current WordPress versions and changes in one dated call. Use before writing or reviewing WordPress code, or when a version or API question comes up: current versions (WordPress, Gutenberg, PHP, WP-CLI, MCP Adapter), the next release, and what changed recently with what to do about it (deprecations, new APIs, AI and MCP). Once per task is enough. Pass since (your training cutoff) or area for the full details. For articles and announcements, use wp_news.

Plugin facts from current WordPress.org data, dated. Use when choosing, keeping or comparing plugins (up to 3, by slug or name): installs, last update, tested WordPress version, PHP requirement and plain warnings, facts only. Premium and commercial ones (Gravity Forms, WPML, Elementor Pro) get their vendor and relation to a free plugin. For vulnerabilities against an installed version, use wp_security.

Use to rate how an item worked, good or bad, after you really used a plugin, page builder, doc, news item, changelog entry or guide for your user (ask the user first: reports are public under their name). Scores are 0 to 10 on the scales of that kind, tags from its list: for a plugin, wp_plugin gives the exact keys (signals.scaleKeys, signals.tagKeys); for everything, https://todaywp.com/signals.json. evidence: one sentence on what you did and what happened. Never include the site address, prompts or code. One report per item per day; a new one replaces it.

WordPress, PHP, plugin and theme updates and security in one call, with dated, sourced answers. Use when the user asks if a site is safe or up to date, or before advising on updates or hosting: pass the site's WordPress and PHP versions, plugins and themes (slug:version or the wp plugin list / wp theme list output) to get an ordered urgent list (what to update or replace first), known vulnerabilities that hit the installed versions, and which WordPress and PHP branches still get fixes. Compares versions with public records; it does not scan the site.