You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Compact tools/list for a typical sales agent is ~494 KB, nearly 4x AdCP's 128 KiB target, mostly output schemas #1909
get_tools_for_handler(..., schema_mode="compact"), the default serve() uses, still produces a tools/list page well over AdCP's 128 KiB target for a typical sales agent. Most of the size is response schemas.
AdCP asks:
Servers SHOULD paginate the live tool catalog so each page remains under the same 128 KiB target. … do not publish the full AdCP catalog, response schemas, or long reference prose in a session's tools/list result.
The tools: get_adcp_capabilities, get_products, create_media_buy, update_media_buy, get_media_buys, get_media_buy_delivery, sync_creatives, list_creatives, list_creative_formats, list_accounts, sync_accounts, get_signals, activate_signal and provide_performance_feedback.
The largest entries are get_products (103,937 B), create_media_buy (97,703 B), update_media_buy (60,114 B), get_media_buys (37,765 B), get_media_buy_delivery (37,246 B) and sync_creatives (33,919 B).
For comparison, the static ADCP_TOOL_DEFINITIONS input schemas total 13,592 B for all 83 tools.
Why it matters
AdCP's own target is 128 KiB per page, so the default sales surface is about 3.8 times over it.
Clients that load tools/list into a model pay for all of it on every session.
Leave outputSchema out of tools/list by default. It's optional in MCP, AdCP asks agents not to publish response schemas there, and it's 45% of this page. An opt-in could keep it for clients that want it.
Bound the compact input schema further: root fields, plus required nested fields to one level, plus a pointer to the bundled schema for the rest. That keeps a 14-tool sales page under 128 KiB.
Activity