Tap

View saved version →

---
name: review-broadcast-campaigns
description: Review Tap TV and radio campaigns, prepare unsent broadcast RFPs, check readiness, and compare submitted supplier responses. Use for buyer planning and RFP requests in Tap.
---

# Review broadcast campaigns in Tap

Use the connected Tap MCP tools for current buyer-workspace data. Match the
user's named campaign before making changes; ask which campaign when multiple
matches remain. Tool names retain `Plan` and `Avail` for compatibility; call
these campaigns and supplier responses in the answer.

## Review campaigns and gaps

Use `listMyPlans` to identify visible campaigns. Its summary does not contain
all completion fields. When asked for missing details, retrieve
`getPlanContext` for each campaign being assessed and check budget, objective,
audience, flight, markets, and media against that context. Distinguish an
optional unassigned brand from a required RFP completion issue. Missing fields
in a list projection are unknown until the detailed context is retrieved.

Report concrete gaps without filling them with guesses. A request to review
does not authorize saving edits.

## Prepare or update broadcast RFPs

Retrieve current campaign context and matching RFP details first. Reuse a
matching existing draft when appropriate and explicitly say it already
existed. Use `createBroadcastRfpDrafts` only when creation is needed; distinguish
its created and already-existing results. Preserve issued RFPs when editing
campaign drafts.

Ground station choices in `listBroadcastRecipientCandidates` and current
recipient records. Do not invent stations, recipients, rates, or availability.
Use `stageBroadcastRfpRecipients` only when a recipient change is requested or
needed for the requested preparation; replacing the saved selection requires
approval. Preparing a draft does not send it.

For readiness reviews, use `listBroadcastRfps` and `getBroadcastRfp`. Separate
sent RFPs from drafts, report each draft's completion issues, and distinguish
"ready to send" from "sent". A draft with no selected recipient is not ready.

## Review submitted responses

Use `getBroadcastBuyingContext` and `assembleBroadcastBuy` for the requested
campaign and medium. Compare submitted options using their actual quoted
rates, quantities, audience, dates, and weekly goals. Explain the recommended
option, total cost, projected impressions, effective CPM, uncovered goals, and
remaining budget where the tools provide them. Keep proposed and saved buys
distinct; calculation alone does not save or select a composition.

## Approval and supported scope

Before an external send or destructive change, state the specific campaign or
RFP, affected fields or recipients, and consequence. Respect the host's action
permissions and confirmation prompts; the OpenAI plugin uses this native flow.
Complete any additional approval requested by the server. A request to skip the
preview does not remove the need to explain the consequence.
Approval of a budget change does not authorize recipient changes or sending.
Do not fabricate approval responses or treat an approval error as success.
If approval is declined, cancelled, or unsupported, stop that action, state
that nothing changed, and provide the tool's Tap recovery link when available.

This plugin cannot delete all client data or an entire organization. Do not
offer bulk campaign, RFP, response, or organization deletion, and do not ask a
user to confirm an unsupported deletion. Supported brand and memory deletion
still requires specific identifiers, a stated consequence, and approval.

The plugin cannot create or send supplier orders, book media, make payments,
or execute trades. Explain this limitation when asked; preparing or selecting
a buy recommendation is not a booking. Do not redirect a booking or payment
request to another tool as a workaround.

## Present the result

Use the returned text and structured data as the source of truth. Present the
results directly in the conversation using concise text or a comparison table.
Include returned Tap links when useful. Summarize what was found, what changed, what
remains incomplete, and whether anything was sent. Do not expose diagnostic
identifiers or unrelated account data. Direct sign-in through Tap OAuth;
never ask for passwords, tokens, or payment details in the conversation.

Referenced files: 1