Every change Wellknown observed on this MCP server, newest first, with what it was before and what it became. Tool-surface changes carry the definition diff. Nothing here is edited after the fact.
Changed the definition of "export_dataset" and "get_social_attention"
{"$schema":"http://json-schema.org/draft-07/schema#","additionalProperties":falsetrue,"properties":{"cursor":{"description":" ⟨117 unchanged words⟩ "type":"array"}},"type":"object"},"format":{"description":"Export format (default: json). Currently only JSON is supported.","enum":["json"],"type":"string"}},"required":["dataset","filters" ⟨2 unchanged words⟩
Query measured social attentioncontagion metrics fromeventsthewithinobservationyourstream.authorizedReturnsscreenwindowsandwherevenueattentionscope.propagatedFilterbetweenbyviewersminimum(social amplification factor> 1). Social attention data is produced by the AttentionGraphBuilder running on CTV edge devices, which models viewer attention as a directed graph
Recently observed → Live
Live → Recently observed
Changed the definition of "purchase_credits"
{"$schema":"http://json-schema.org/draft-07/schema#","additionalProperties":false,"properties":{"idempotency_key":{"description":"Stable logical purchase ID. Reuse it for retries of the same purchase; use a new value for a new credit order.","maxLength":256,"minLength":1,"type":"string"},"tier":{"description":"Credit purchase tier", ⟨4 unchanged words⟩ type":"string"}},"required":["tier","idempotency_key"],"type":"object"}
Added "configure_feedback_brand", "create_creative_experiment", "generate_brand_creative" and 7 more; removed "describe_endpoint", "get_content_performance", "get_content_recommendations" and 7 more; changed the definition of "setup_billing"
Set up pay-per-use billing with a Stripe payment method.RequiredAafterstoredexceedingcardfreegrantstiernolimits.API credit; fund usage with credits or explicitly authorized API postpay allowance. Pass a Stripe payment method token (pm_xxx) ⟨6 unchanged words⟩
Changed the definition of "semantic_search_observations"
⟨163 unchanged words⟩ the window actually applied is echoed in metadata.time_range.Observations are retained for 90 days.WHEN TO USE: - Finding observations that ⟨127 unchanged words⟩
Servers that share this record's repository now have records of their own: "trillboards-connect". Checks before this date include them.
Changed the definition of "export_dataset"
⟨10 unchanged words⟩ time, geography, venue type, and observation family.Applies k-anonymity (k=5) to protect individual privacy.Queries the relevant table based on the selected dataset type, applies filters,enforcesandk-anonymityreturnsbyeverysuppressingmatchinggroupsrowwithasfewerstructuredthandata,
Removed "comply_test_controller" (84 tools before, 83 now)
[AdCP Deterministic Testing] Force state transitions for compliance runs. Sandbox accounts only; live accounts get FORBIDDEN. scenario=list_scenarios enumerates.
Certificate changed, valid to 2026-12-12
Certificate recorded, valid to 2026-12-08
Authorization not required
npm:@trillboards/connect (package_npm) — from npm
First tool surface recorded: 84 tools (server version 1.0.0)
Showing the latest 14 events. The API returns up to 500 and filters by kind: ?kind=tool_surface_changed
Configure your native brand profile and enable its booked reactive campaign. Uses your authenticated native buyer and existing funded placement.
Create an experiment on a funded native media-buy placement. Uses your authenticated native buyer and existing funded placement.
Generate a native brand creative for explicit review and moderation. The native ad and advertiser come from the experiment. Review and AI moderation are separate. The existing data_api/api_calls tariff applies.
Read your native experiment, policy and latest 500 owned creative recovery records. Uses your authenticated native buyer and existing funded placement.
Read a metered page of latest measured native play states. Read actual latest native plays with NULL preserved. Dates are YYYY-MM-DD, max 31 days. Poll with the returned cursor; canonical_key plus reward_revision_id identify logical changes; build_stamp is provenance. Each page uses the published data_api/api_calls tariff.
Import an AI model’s image through native bytes, moderation and brand review. Provide exactly one of asset_url, source_creative_id or image_base64. Inline bytes require content_type. PNG, JPEG and WebP are staged through native ownership, actual MIME, byte-hash, brand review and moderation. The existing data_api/api_calls tariff applies.
Register approved native generated creative variants. Uses your authenticated native buyer and existing funded placement.
Approve or reject your generated creative using native brand review. Uses your authenticated native buyer and existing funded placement.
Stop the native experiment at the expected policy version. Uses your authenticated native buyer and existing funded placement.
Replace native creative weights at the expected policy version. Uses your authenticated native buyer and existing funded placement.
Describe a single API operation including its parameters, response shape, and error codes. WHEN TO USE: - Inspecting an endpoint's full contract before calling it. - Discovering which error codes an endpoint can return and how to recover. RETURNS: - operation: Full discovery record for the endpoint. - parameters: Raw OpenAPI parameter definitions. - request_body: Body schema (when applicable). - responses: Map of status code → description/schema. - linked_error_codes: Error catalog entries the endpoint can emit. EXAMPLE: Agent: "How do I call the screen audience endpoint?" describe_endpoin…
Get performance metrics for a video across the Trillboards DOOH network. WHEN TO USE: - Checking how a specific video performs across screens (plays, attention, audience size) - Analyzing which venue types and dayparts a video resonates best in - Finding the top-performing screens for a piece of content - Comparing content performance over different time windows RETURNS: - videoId, title, totalPlays, uniqueScreens - avgAttention (0-1), avgAudienceSize, avgDwellMs - venueDistribution: Array of { venue_type, plays } - daypartDistribution: Array of { daypart, plays } - topScreens: Top 10 scree…
Get best-performing content recommendations for a venue type and optional time context. WHEN TO USE: - Deciding what content to schedule at a specific venue type - Finding content that drives the highest audience engagement at a location - Optimizing content rotation by daypart (morning, afternoon, evening, overnight) - Content programming decisions based on performance data RETURNS: - data: Array of recommended content ranked by performance score - videoId, title, contentCategory, durationSeconds - totalPlays, uniqueScreens - avgAttention (0-1), avgDwellMs - performanceScore (compo…
Get statistics about available causal training data: total tuples, unique creatives, venue diversity, date range. Queries observation_stream for rows that have both a creative ID and a VAS outcome recorded, giving a picture of how much training data is available for the causal prediction engine. WHEN TO USE: - Checking if enough data exists for reliable causal predictions - Understanding the diversity of training data (creatives, venues, time range) - Monitoring causal dataset health and growth - Planning data collection strategies RETURNS: - data: Dataset statistics - total_tuples: numb…
Aggregate social attention metrics across screens and time periods. Shows which venues and dayparts have the highest social amplification. Queries observation_stream for social attention data and aggregates by the requested dimension (venue, daypart, or screen), computing average SAF, average cascade depth, average viral attention score, and event count. WHEN TO USE: - Understanding which venues generate the most social amplification - Comparing daypart effectiveness for social contagion - Identifying top-performing screens for attention cascading - Planning campaigns that leverage social p…
List every registered Trillboards API operation. WHEN TO USE: - First call in an agent session to learn what the API offers. - Filter to agent_safe=true to list only side-effect-free endpoints. - Narrow to a single surface (data-api, sdk-api, device-api, sensing-api, partner-api-generated, dsp-api-generated). RETURNS: - operations: Array of { surface, method, path, operation_id, summary, description, agent_safe, idempotent, cost_tier, tags, doc_url, example_request } - total_operations: Total count. - surfaces: Known surface identifiers. EXAMPLE: Agent: "What read-only endpoints can …
List every error code in the Trillboards API error catalog. WHEN TO USE: - Understanding what error codes the API can return. - Building a client-side error handler that covers all cases. - Looking up error types, HTTP statuses, and documentation URLs. RETURNS: - object: "list" - data: Array of { code, type, http_status, description, doc_url } - total: Total number of error codes. Equivalent to GET /v1/errors but executed in-process (no HTTP round-trip). EXAMPLE: Agent: "What error codes can the API return?" list_error_codes()
Query the Trillboards API changelog for recent changes, breaking changes, deprecations, and fixes. WHEN TO USE: - Check what has changed in the API before upgrading an integration. - Find breaking changes since a specific date. - Discover new features added to a specific API surface. PARAMETERS: - since (YYYY-MM-DD, optional): Only entries dated on or after this date. Unreleased entries are always included. - type (string, optional): Filter by change category. Accepts: "breaking" → changed + removed entries "additive" → added entries "deprecation" → deprecated entries …
Semantic search over content library using natural language queries and 768-D pgvector embeddings. WHEN TO USE: - Finding content by description or theme ("upbeat music videos", "cooking shows") - Discovering content similar to a concept or mood - Searching the content library without knowing exact titles or IDs - Content discovery for programmatic content scheduling RETURNS: - data: Array of matching content with similarity scores - videoId, title, contentCategory, description, durationSeconds - reviewStatus (approved/pending/rejected) - similarity (0-1, cosine similarity against que…
Validate a proposed request payload against the registered Zod schema for an operation, returning the exact canonical error envelope the HTTP surface would emit. WHEN TO USE: - Before calling a write endpoint, to catch payload bugs locally. - Debugging 400 validation_error responses. RETURNS: - valid: true when the payload would pass Zod validation. - When invalid, the canonical { error: { type, code, message, param, doc_url, details[] } } envelope is included under `error`. EXAMPLE: validate_request({ path: "/v1/data/query", method: "POST", payload: { dataset: "inference_outcomes"…
{"$schema":"http://json-schema.org/draft-07/schema#","additionalProperties":false,"properties":{"cursor":{"description":"The previous page's metadata.next_cursor, to read the next page (same dataset and filters).","maxLength":2000,"type":"string"},"dataset":{"description":"Type of dataset to ⟨118 unchanged words⟩