call-adcp-agent

Enforce wire-level invariants for AdCP buyer calls across MCP and A2A tool surfaces.

1|5|Updated Nov 5, 2025

Search Tags:#agent #async #error-handling #idempotency #adcp #oneof #account-variant

Ready to run

npx skills add https://github.com/adcontextprotocol/adcp-client-python --skill call-adcp-agent

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: call-adcp-agent
Source: https://github.com/adcontextprotocol/adcp-client-python/tree/main/skills/call-adcp-agent
Command: npx skills add https://github.com/adcontextprotocol/adcp-client-python --skill call-adcp-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Wire-level invariants for AdCP buyer calls—idempotency_key replay semantics, account oneOf variants, and async status/polling semantics—are defined to ensure safe, repeatable interactions with AdCP agents.

Core Features & Use Cases

Enforces idempotency_key replay semantics for mutating tools to ensure deterministic responses on retries.
Validates account oneOf variants (seller-assigned account_id vs natural-key brand/operator) to avoid mixing fields across variants.
Handles async status sequences with status:'submitted' and task_id polling, while cleaning up error envelopes with adcp_error.issues for rapid recovery.
Provides guidance for cross-cutting error recovery and recommended loading order before per-protocol task skills.

Quick Start

Load this skill before any per-protocol AdCP buyer call skill to ensure invariants are established during agent interactions.

Frequently Asked Questions about call-adcp-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce idempotency key replay semantics for AdCP buyer calls?▼

To enforce idempotency key replay semantics for AdCP buyer calls, load this skill before per-protocol tasks to ensure mutating tools return deterministic responses during network retries.

What is the best way to validate account oneOf variants in AdCP protocols?▼

Validating account oneOf variants in AdCP protocols requires checking that seller-assigned account_id and natural-key brand/operator fields are never mixed, preventing malformed buyer requests.

How do I handle async status polling and submitted task_id sequences in AdCP?▼

Handling async status polling in AdCP involves processing status:'submitted' responses and polling the task_id until completion, while cleaning up error envelopes via adcp_error.issues for rapid recovery.

Do I need to load a base skill before calling AdCP media buy or creative agents?▼

Yes, you must load this skill before any per-protocol AdCP buyer call skill, such as adcp-media-buy or adcp-creative, to establish wire-level invariants across MCP and A2A tool surfaces.

Why does my AdCP agent return inconsistent errors across get_products and create_media_buy?▼

Inconsistent errors across get_products and create_media_buy occur without standardized wire-level invariants; applying adcp_error.issues standardizes error handling and ensures consistent cross-cutting recovery.