WordPress spreads your content out. Posts here, pages there, products in their own place, and whatever custom post types your theme or plugins have added off in their own corners. Most of the time you never notice, because you work on one type at a time. But every so often you need to find something everywhere it lives at once, and then the split becomes the problem. You end up searching posts, then searching pages, then remembering the product catalog, then wondering what custom types you forgot. Agent Abilities for MCP gives an agent a single search that spans every post type in one pass, so you ask once instead.
Ask once, see all of it
The ability is search-content, and the useful thing about it is the scope. It does not search one post type and make you repeat the query for the next. It runs a single search across every post type at the same time and comes back with each place your term shows up, whatever kind of content it is sitting in.
That turns a scavenger hunt into one question. Say you renamed a product and want every stray mention of the old name. Or a URL changed and you need to find everywhere the old link is still written into your content. Or you made a claim in an old post, a price, a stat, a promise, and you want to know everywhere you repeated it before you go correcting it. One search covers posts, pages, products, and your custom types together, and you get the full list back in one place rather than assembling it type by type in your head.
Why this matters before you change anything
The moment this really earns its place is right before you change or delete something. That is exactly when you want to know the blast radius.
Deleting a page feels small until you find out three posts linked to it and a product referenced it. Renaming something feels clean until the old name is still sitting in a dozen places you forgot. Editing a claim is easy in the one post you remember and a problem in the four you did not. A single site-wide search, run first, turns all of that from a thing you discover afterward into a thing you see up front. You get the whole footprint of a phrase across every kind of content before you touch any of it, so you are deciding with the full picture instead of hoping you got them all.
That is the difference between an edit you make with your eyes open and one you make and then keep finding leftovers of for weeks.
It only reads
Worth being plain about: search-content is a read. It looks across your content and tells you what it found. It does not change, move, or remove anything on its own. Finding every mention of the old product name is a completely separate act from doing anything about them. The search shows you the map; you decide what, if anything, happens next.
That is what makes it safe to reach for freely. Running it costs you nothing and risks nothing, because all it can do is look. When you do decide to act on what it turned up, that is a different ability with its own gate, and it is your call to make, not a thing the search quietly does for you.
Try it
The matching recipe, Find every mention across your site, has the exact prompt to run and the ability it uses. It pairs naturally with any before-you-edit workflow: search first, look at the spread, then act deliberately.
If you want to see where site-wide search sits among everything else an agent can be given, the abilities catalog lists it alongside the rest, marked as the read it is. Start with a search you already know the answer to, watch it pull every match across every type, and you will have a feel for the one move that saves you the most guesswork later.