Skip to main content
Glama

Buy an Agentry ad product (AdCP)

buy_products
Idempotent

AdCP buy_products: place a fixed-price order for a product from list_products. Agentry stores the order and replies status "submitted" with a task_id; a human reviews it within 3 working days. Then send the article with sync_creatives and track it with get_media_buys. Payment by invoice after publication.

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": {
      "idempotency_key": "<idempotency_key>",
      "feed_version": "<feed_version>",
      "purchases": "<purchases>",
      "start_time": "<start_time>",
      "end_time": "<end_time>"
    },
    "name": "buy_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
brandNo
accountNo
end_timeYes
purchasesYes
start_timeYes
feed_versionYes
total_budgetNo
idempotency_keyYes
pricing_versionNo
purchase_order_refNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

The annotations already declare idempotentHint=true, destructiveHint=false, and readOnlyHint=false. The description adds real behavioral context beyond that: the reply status is 'submitted' with a task_id, a human reviews it within 3 working days, and payment is by invoice after publication. It omits what happens if the human review rejects the order, so it falls short of a 5.

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 tight sentences are ordered by priority: the action, then the async outcome, then the follow-up and payment. The only waste is the leading 'AdCP buy_products:' label, which repeats the tool name and title.

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

Completeness2/5

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

For a tool with heavy nesting, 11 parameters, 5 required fields, and no output schema, the description covers only the workflow and the order's fate. It does not explain the required inputs an agent must supply to succeed, which is the biggest risk for this tool.

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

Parameters2/5

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

Schema description coverage is 0% across 11 parameters, including 5 required ones, yet the description explains none of them. Required fields such as feed_version and idempotency_key, the maxItems=5 purchases array, total_budget, and the nested brand/account objects are left undocumented, and the start_time's 'asap' const is not mentioned, so the description does not compensate for the schema gap.

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?

The description uses a specific verb and resource: 'place a fixed-price order for a product from list_products'. This clearly distinguishes the tool from read-side siblings such as list_products and get_media_buys. However, it never contrasts this tool with create_media_buy, the closest sibling, so an agent must infer which one to use.

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?

The description gives clear workflow guidance: it names list_products as the prerequisite source of the product, then says to send the article with sync_creatives and track it with get_media_buys. It does not say when not to use it, and it does not place it relative to create_media_buy.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources