Skip to main content
Glama

The Profound Agency

by io.github.Jfromtheroc
OverviewDiscussionsAdmin

Plan placements

plan_placements
Read-only

Recommend a set of publications for a goal, audience and budget — already quoted, total inside budget including the 3.5% processing fee. Use this when a buyer says what they want to achieve and what they can spend, rather than naming publications. A backlink or SEO goal leaves out nofollow links. The shareUrl opens the store with the planned placements in the cart (none when a niche price applies); the plan recommends, it reserves nothing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalNoWhat the coverage is for, e.g. "seo backlinks", "launch buzz".
countNoHow many placements to aim for. Default 5.
nicheNoThe restricted subject the article is on, if any: CBD, Crypto, Health, Gambling or Erotic. Priced at the outlet's price for that niche, and refused where the outlet doesn't accept it.
budgetYesMaximum spend in USD, including the processing fee.
audienceNoCatalog categories or genres, e.g. ["Crypto", "Health"].
minMonthlyTrafficNoMinimum estimated monthly visits to the outlet's site.
minDomainAuthorityNoMinimum Moz Domain Authority.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / audience / description
      Previous value: -"Catalog categories, e.g. [\"Crypto\", \"Health\"]."New value: +"Catalog categories or genres, e.g. [\"Crypto\", \"Health\"]."
    • addedInput schema / properties / minMonthlyTraffic
      Added value: +{
+  "description": "Minimum estimated monthly visits to the outlet's site.",
+  "minimum": 0,
+  "type": "number"
+}
    • addedInput schema / properties / niche
      Added value: +{
+  "description": "The restricted subject the article is on, if any: CBD, Crypto, Health, Gambling or Erotic. Priced at the outlet's price for that niche, and refused where the outlet doesn't accept it.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the read-only, non-destructive, closed-world profile, and the description adds genuinely new behavior: the total includes a 3.5% processing fee, backlink/SEO goals exclude nofollow links, the shareUrl pre-loads the cart (empty when niche pricing applies), and nothing is reserved. That is substantive context an agent cannot infer from the annotation triple.

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?

Front-loaded with the core recommendation purpose, and every clause carries information (fee, nofollow, shareUrl, non-reserving). It is dense with parentheticals and semicolons, which slightly taxes readability, but nothing is padding.

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

Completeness5/5

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

With no output schema and a read-only annotation profile, the description supplies what the agent needs: how budget is computed, what the plan excludes, what the returned shareUrl does, and that no inventory is reserved. All 7 parameters are documented at 100% coverage, leaving no obvious gap.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds semantic meaning beyond the schema: budget is inclusive of the processing fee, goal wording drives nofollow filtering, and the niche/price relationship explains the empty-cart case. It stops short of adding per-parameter syntax the schema lacks.

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 ('Recommend a set of publications') scoped to goal/audience/budget, and explains it is pre-quoted within budget. It also implicitly separates itself from the naming-based siblings via 'rather than naming publications', so an agent can route without opening any schema.

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

Usage Guidelines4/5

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

Gives a clear trigger condition: use it when a buyer states an outcome and a spend limit instead of naming publications. It does not explicitly name the alternative tools (quote_placements, search_placements, compare_placements) that handle the naming case, so the routing is implied rather than spelled out.

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