Skip to main content
Glama

The Profound Agency

by io.github.Jfromtheroc
OverviewDiscussionsAdmin

Search placements

search_placements
Read-only

Search the publisher network for editorial placements. Filter by price, Domain Authority, Domain Rating, category, region, turnaround and whether the outlet is Google-indexed or LLM-ready, link type and availability. Returns a page of matches, highest Domain Authority first by default. Each result carries the same fields as get_placement.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNo
limitNoResults per page, 1-100. Default 20.
queryNoFree text matched against publication name, domain and categories.
offsetNoResult offset, for paging.
regionNoSubstring match on the outlet's region.
llmReadyNoOnly outlets flagged as readable by AI crawlers.
maxPriceNoMaximum price in USD.
minPriceNoMinimum price in USD.
availableNotrue for placements that can be ordered now, false for unavailable ones.
categoriesNoMatch any of these categories, e.g. ["Crypto", "Health"].
linkFollowNoOnly placements with this linkAttributes value. Today the catalog records dofollow only; every other listing is "unspecified", so nofollow, sponsored and ugc match nothing yet.
googleIndexedNoOnly outlets known to be indexed by Google.
minDomainRatingNoMinimum Ahrefs Domain Rating (0-100).
maxTurnaroundDaysNoLongest acceptable turnaround, in days.
minDomainAuthorityNoMinimum Moz Domain Authority (0-100).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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"
+}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral detail beyond that: results are paged ('returns a page of matches'), default ordering is highest Domain Authority first, and the result shape mirrors get_placement. It omits whether results are cached/rate-limited, which is minor for a read-only search.

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

Conciseness4/5

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

Three sentences, front-loaded with purpose then filters then return behavior; no filler. It could have been tighter by folding the filter list, but each sentence carries distinct information.

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?

For a 15-parameter, zero-required, read-only search tool with no output schema, the description adequately covers what can be searched, how results are ordered and paged, and what a result looks like. It stops short of naming the sort enum values or paging limits, but those are fully documented in the schema.

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 description coverage is 93%, so the schema already documents nearly every parameter, including the dofollow caveat and the paging fields. The description's filter enumeration ('price, Domain Authority, Domain Rating, category, region, turnaround... link type and availability') largely restates what the schema already conveys, adding little beyond the default-sort behavior that the schema omits. Baseline 3 is appropriate.

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

Purpose5/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 immediately enumerates the filterable dimensions, which distinguishes it from the single-record sibling get_placement and from comparison tools like compare_placements and quote_placements.

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?

The mention that 'each result carries the same fields as get_placement' implies this is the bulk-discovery counterpart to the single-placement lookup, but the description never states when to search versus when to call get_placement, get_availability, or compare_placements directly. Usage is implied rather than prescribed, and no exclusions or prerequisites are given.

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 toolsInspect
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.

Resources