The Profound Agency

Search placements

search_placements

Read-only

Search the publisher network for editorial placements. Filter by price, Domain Authority, Domain Rating, monthly traffic, category, genre, region, turnaround, link type (dofollow or nofollow), whether the outlet is Google-indexed or LLM-ready, a restricted niche it accepts, and availability. Returns a page of matches, highest Domain Authority first by default. Each result carries the same fields as get_placement; a search with niche adds nichePrice, the price of an article in that niche.

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	Default da_desc. traffic_desc is most monthly visits first. Missing values sort last.
`limit`	No	Results per page, 1-100. Default 20.
`niche`	No	Only outlets that accept articles on this restricted subject: CBD, Crypto, Health, Gambling or Erotic. Results then carry nichePrice, and minPrice, maxPrice and the price sorts use it.
`query`	No	Free text matched against publication name, domain, categories and genres.
`genres`	No	Match any of these genres, what the outlet covers, e.g. ["Tech", "Finance"]. A word matches either side of a compound genre: "Crypto" matches "Crypto & Web3". list_categories lists them.
`offset`	No	Result offset, for paging.
`region`	No	Substring match on the outlet's region.
`llmReady`	No	Only outlets flagged as readable by AI crawlers.
`maxPrice`	No	Maximum price in USD.
`minPrice`	No	Minimum price in USD.
`available`	No	true for placements that can be ordered now, false for unavailable ones.
`categories`	No	Match any of these categories, e.g. ["Crypto", "Health"].
`linkFollow`	No	Only placements with this linkAttributes value: "dofollow" or "nofollow" as the catalog records the link, "unspecified" where it has no record. Nothing records sponsored or ugc, so those match nothing.
`googleIndexed`	No	Only outlets known to be indexed by Google.
`minDomainRating`	No	Minimum Ahrefs Domain Rating (0-100).
`maxTurnaroundDays`	No	Longest acceptable turnaround, in days.
`minMonthlyTraffic`	No	Minimum estimated monthly visits to the outlet's site. Outlets with no traffic figure are left out.
`minDomainAuthority`	No	Minimum Moz Domain Authority (0-100).

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 14, 2026

addedInput schema / properties / genres

Added value: +{
+  "description": "Match any of these genres, what the outlet covers, e.g. [\"Tech\", \"Finance\"]. A word matches either side of a compound genre: \"Crypto\" matches \"Crypto & Web3\". list_categories lists them.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / linkFollow / description

Previous value: -"Only placements with this linkAttributes value. Today the catalog records dofollow only; every other listing is \"unspecified\", so nofollow, sponsored and ugc match nothing yet."New value: +"Only placements with this linkAttributes value: \"dofollow\" or \"nofollow\" as the catalog records the link, \"unspecified\" where it has no record. Nothing records sponsored or ugc, so those match nothing."

addedInput schema / properties / minMonthlyTraffic

Added value: +{
+  "description": "Minimum estimated monthly visits to the outlet's site. Outlets with no traffic figure are left out.",
+  "type": "number"
+}

addedInput schema / properties / niche

Added value: +{
+  "description": "Only outlets that accept articles on this restricted subject: CBD, Crypto, Health, Gambling or Erotic. Results then carry nichePrice, and minPrice, maxPrice and the price sorts use it.",
+  "type": "string"
+}

changedInput schema / properties / query / description

Previous value: -"Free text matched against publication name, domain and categories."New value: +"Free text matched against publication name, domain, categories and genres."

addedInput schema / properties / sort / description

Added value: +"Default da_desc. traffic_desc is most monthly visits first. Missing values sort last."

changedInput schema / properties / sort / enum

Previous value: -[
-  "price_asc",
-  "price_desc",
-  "da_desc",
-  "dr_desc",
-  "turnaround_asc"
-]New value: +[
+  "price_asc",
+  "price_desc",
+  "da_desc",
+  "dr_desc",
+  "turnaround_asc",
+  "traffic_desc"
+]

Changed2 schema fields changedOct 2, 2026

addedInput schema / properties / available

Added value: +{
+  "description": "true for placements that can be ordered now, false for unavailable ones.",
+  "type": "boolean"
+}

addedInput schema / properties / linkFollow

Added value: +{
+  "description": "Only placements with this linkAttributes value. Today the catalog records dofollow only; every other listing is \"unspecified\", so nofollow, sponsored and ugc match nothing yet.",
+  "enum": [
+    "dofollow",
+    "nofollow",
+    "sponsored",
+    "ugc",
+    "unspecified"
+  ],
+  "type": "string"
+}

First observedOct 2, 2026

TDQS

A3.8/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare read-only, non-destructive, and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: results are paged, defaulted to highest Domain Authority first, mirror get_placement's field set, and gain nichePrice when a niche filter is applied. It does not mention rate limits or what the response looks like when zero filters are supplied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause, the filter surface follows, and return behavior closes the description. Two dense sentences with essentially no filler, and the long filter list is earned by 18 parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of explaining returns and does so: paging, default ordering, per-result fields, and the nichePrice addition. For a broad search tool this is close to complete, though it omits behavior with no filters applied and any result-count or rate considerations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and every parameter already carries a description, so the baseline is 3. The description's filter enumeration largely restates the schema, including the niche/nichePrice and price-sort interaction that is already documented on the niche parameter, adding little beyond what structured data provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search the publisher network for editorial placements') and enumerates the filterable dimensions, so an agent knows exactly what the tool does. It implicitly contrasts with get_placement via 'each result carries the same fields as get_placement', but never names the closer siblings (compare_placements, plan_placements, quote_placements) to differentiate itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the description is a catalog search, so an agent can infer it is for discovery, and the niche/price interaction hints at a planning workflow. However, there is no explicit when-to-use, no when-not-to-use, and no routing to alternatives such as compare_placements or quote_placements for follow-up steps.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All The Profound Agency tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Search placements

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources