Context
The public test agent (test-mcp / https://test-agent.adcontextprotocol.org/mcp/) is a media buy seller. It lacks tools for three protocol domains, which means their storyboards are entirely skipped during compliance testing:
- Property governance:
create_property_list, list_property_lists, get_property_list, update_property_list, delete_property_list, validate_property_delivery
- Content standards:
list_content_standards, get_content_standards, create_content_standards, update_content_standards, calibrate_content, validate_content_delivery
- Brand rights:
creative_approval (the agent has get_brand_identity, get_rights, and acquire_rights but is missing creative_approval)
Additionally, the get_brand_identity request builder resolves the brand to the agent's own domain (test.example) rather than using the storyboard's sample_request brand ID (acme_outdoor). This means the brand resolution verification added in #507 fails — not because the storyboard is wrong, but because the request builder ignores the fictional entity.
Storyboard results against test-mcp
| Storyboard |
Passed |
Failed |
Skipped |
Notes |
brand_rights |
3 |
1 |
4 |
get_brand_identity fails (wrong brand resolved); creative_approval steps skipped (missing tool) |
property_governance |
0 |
0 |
8 |
All steps skipped — no governance tools |
content_standards |
0 |
0 |
9 |
All steps skipped — no governance tools |
What needs to happen
- Add governance tools to the test agent (or stand up a separate governance test agent) so
property_governance and content_standards storyboards can execute
- Add
creative_approval tool so the brand rights storyboard can run end-to-end
- Fix
get_brand_identity request builder to respect the sample_request.brand_id from the storyboard YAML instead of overriding it with resolveBrand(options).domain. The fictional entities in storyboards/fictional-entities.yaml (e.g., acme_outdoor) should be resolvable by the test agent.
- Seed fictional entities — the test agent should recognize the sandbox brands from
fictional-entities.yaml (acme_outdoor, nova_motors, bistro_oranje, etc.) for brand identity lookups
Reproduction
npx @adcp/client storyboard run test-mcp brand_rights --json
npx @adcp/client storyboard run test-mcp property_governance --json
npx @adcp/client storyboard run test-mcp content_standards --json
Related
Context
The public test agent (
test-mcp/https://test-agent.adcontextprotocol.org/mcp/) is a media buy seller. It lacks tools for three protocol domains, which means their storyboards are entirely skipped during compliance testing:create_property_list,list_property_lists,get_property_list,update_property_list,delete_property_list,validate_property_deliverylist_content_standards,get_content_standards,create_content_standards,update_content_standards,calibrate_content,validate_content_deliverycreative_approval(the agent hasget_brand_identity,get_rights, andacquire_rightsbut is missingcreative_approval)Additionally, the
get_brand_identityrequest builder resolves the brand to the agent's own domain (test.example) rather than using the storyboard'ssample_requestbrand ID (acme_outdoor). This means the brand resolution verification added in #507 fails — not because the storyboard is wrong, but because the request builder ignores the fictional entity.Storyboard results against test-mcp
brand_rightsget_brand_identityfails (wrong brand resolved);creative_approvalsteps skipped (missing tool)property_governancecontent_standardsWhat needs to happen
property_governanceandcontent_standardsstoryboards can executecreative_approvaltool so the brand rights storyboard can run end-to-endget_brand_identityrequest builder to respect thesample_request.brand_idfrom the storyboard YAML instead of overriding it withresolveBrand(options).domain. The fictional entities instoryboards/fictional-entities.yaml(e.g.,acme_outdoor) should be resolvable by the test agent.fictional-entities.yaml(acme_outdoor,nova_motors,bistro_oranje, etc.) for brand identity lookupsReproduction
Related