The Profound Agency

Create order

create_order

Open a pending order for a client and return a payment link. IMPORTANT: this does not pay for anything. The order stays unpaid until a human opens the returned payUrl and pays on the store's checkout. Give the link to the client or to someone at your agency — you cannot complete payment yourself, and you must not tell the client the placement is bought until check_order_status reports paid: true. Confirm the placements and the total with a human before calling this. No account or API key is required, but an unpaid order is deleted automatically after 72 hours, so send the link promptly.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "items": "<items>",
      "contact": "<contact>"
    },
    "name": "create_order"
  }
}

Input Schema

Name	Required	Description
`items`	Yes
`notes`	No	Anything the editorial team should know.
`contact`	Yes
`placedBy`	No	Who you are — your agency or product name. Recorded as an unverified claim, purely so we can tell orders apart.
`clientReference`	No	Your own reference for this client or campaign.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

addedInput schema / properties / items / items / 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"
+}

Changed2 schema fields changedOct 5, 2026
- changedInput schema / properties / items / items / properties / quantity / description
```
Previous value: -"Defaults to 1."New value: +"How many of this placement; at least 1. Defaults to 1."
```
- changedInput schema / properties / items / items / properties / quantity / minimum
```
Previous value: --9007199254740991New value: +1
```
First observedOct 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations only cover the safety profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false, openWorldHint=false). The description goes far beyond: the order stays pending until a human pays externally, no account/API key is needed, and unpaid orders are auto-deleted after 72 hours. These are non-obvious lifecycle and side-effect facts an agent cannot derive from structured fields.

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 purpose and the critical 'does not pay for anything' warning in caps before any secondary detail. It is longer than most definitions but nearly every sentence carries an actionable constraint; only the API-key remark is somewhat tangential.

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?

There is no output schema, so the description carries return-value burden and does so by naming the returned payUrl and the mechanism by which payment completes. Combined with the lifecycle and human-in-the-loop constraints, an agent has everything needed to call and follow up correctly.

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 60% with nested item objects, and the schema itself documents id/niche/quantity/contact.email. The description adds only indirect mapping ('give the link to the client' → contact.email, 'confirm the placements and total' → items). It does not explain quantity, niche pricing behavior, or placedBy semantics beyond what the schema already states, so the baseline of 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 ('Open a pending order for a client') plus the key side effect ('return a payment link'). It is instantly distinguishable from check_order_status, which it names, and from quote_placements/plan_placements by its ordering intent.

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

Usage Guidelines5/5

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

Explicit prerequisites ('Confirm the placements and the total with a human before calling this'), explicit non-capability ('you cannot complete payment yourself'), an explicit prohibition tied to a sibling ('must not tell the client the placement is bought until check_order_status reports paid: true'), and a timing rule (send the link within 72 hours). Nothing is left to inference.

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.