Skip to main content
Glama

Delivery report for Agentry orders (AdCP)

get_media_buy_delivery
Read-only

AdCP get_media_buy_delivery: how many AI agents read your sponsored article. impressions = reads by AI agents of the article (agent view /agent/, MCP get_story, and AI crawler fetches of the HTML page). Humans are not counted. ext.agentry breaks reads down by agent family (openai, perplexity, anthropic, ...). Counting started 2026-11-09.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_media_buy_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNo
end_dateNoExclusive, YYYY-MM-DD; default tomorrow
start_dateNoInclusive, YYYY-MM-DD; default 30 days ago
media_buy_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare this a safe read (readOnlyHint true, destructiveHint false, closed-world), so the bar is lower, and the description adds real value: the exact surfaces counted (/agent/<slug>, get_story, crawler HTML fetches), the exclusion of humans, and the 2026-11-09 counting start (prior data does not exist). It stops short of describing response shape, aggregation granularity, or latency/limits.

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, metric definition front-loaded before the caveats, with no filler. The 'AdCP get_media_buy_delivery:' prefix partly restates the name/title, a minor redundancy.

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 4-parameter, nested-object read tool with no output schema, the description compensates well by defining the returned metric and its breakdown (ext.agentry by agent family). The main remaining hole is how account/media_buy_ids constrain the report, which neither schema nor description explains.

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 coverage is 50%: start_date/end_date semantics (inclusive/exclusive, defaults) live in the schema, but media_buy_ids and the nested account object are documented nowhere, and the description adds nothing about parameters. It does not mention filtering by media buy or account at all, so the coverage gap is unmitigated.

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 names a specific verb and resource – a delivery report of media-buy impressions – and immediately defines what 'impressions' means (AI agent reads of the sponsored article). That is far more specific than the name alone and distinguishes it from list tools like get_media_buys, though it never explicitly contrasts with a sibling.

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

Usage Guidelines2/5

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

It explains what the report measures but gives no when-to-use / when-not-to-use guidance and names no alternative for related queries (e.g., listing buys versus reporting delivery). The agent must infer the use case from the metric definition.

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