Ambush

Create a feed from a monitoring prompt. To receive its future emissions in this MCP client, subscribe to feed.emission.created using the returned feed_id and webhook delivery. An explicit name is optional. Every accepted headline is delivered the way the owner's profile asks (by default translated into English and cleaned of emojis, tags and markup); pass headline_output to override that for this feed with language (a BCP 47 tag or 'original') and/or clean (boolean), at least one of them. Include post_processing to transform every future accepted event after that and before delivery.

create_feed

Permanently delete an owned feed. This is destructive and should only be called after the user confirms the feed ID.

delete_feed

Get one owned feed, including its current prompt revision, output channels, recent emissions, and usage.

get_feed

List the authenticated user's preconfigured Slack, webhook, Telegram, iMessage, and mobile push destinations. Use a channel whose install status is connected and destination_status is active with route_feed_channel. Labels mask phone numbers, email addresses, and device names, and webhook endpoint paths and internal metadata are redacted; credentials are managed in Ambush and are never requested through this tool.

list_channels

List feeds owned by the authenticated user, newest first. Follow next_cursor to fetch another page. The first page also lists "Streams sent to you from the Ambush app": not a news stream, but the channel the user sends you streams through from the Ambush app.

list_feeds

List the complete emission history for one owned feed, newest first. Follow next_cursor to fetch another page.

list_emissions

Show recent news considered for a stream you own but not selected as a match, newest first, with up to 30 days of available history. Each item includes prompt_revision_id for the saved prompt used in its review, which may predate stream edits. Pass feed_id and optional limit (up to 50, default 20; larger values are capped). Pass next_cursor as cursor to fetch the next page; null means the end. Scores and explanations are not included.

list_near_misses

Set an existing feed-to-channel route active or inactive for future deliveries. Muting permanently cancels pending deliveries and attempts for this route; unmuting does not restore them. The channel credential and feed are not deleted.

update_feed_channel_route

Attach a preconfigured delivery channel to an owned feed. Each future accepted event is processed and enqueued to this destination immediately; this does not poll or retroactively deliver earlier emissions. Repeating the same route safely reactivates it.

route_feed_channel

Tell Ambush what is and isn't working, whenever you notice. About a stream's alerts, with its feed_id: irrelevant_alerts (should not have been sent), missed_news (news it should have caught; check list_near_misses first), duplicate_alerts (one story alerted more than once), late_alerts (too late to be useful), alert_formatting (wrong headline, translation, or post-processed output), working_well. About Ambush itself, feed_id optional: missing_source (an outlet Ambush doesn't watch), tool_error (a call failed or behaved unexpectedly), missing_capability (something the user wanted that Ambush can't do), documentation (wrong or unclear docs). Or other. Cite alerts in emission_ids (with feed_id) and news in news_item_ids, up to 50 each, using only IDs Ambush returned. Ambush reads feedback to improve the product; it changes nothing, so suggest update_feed when a prompt itself should change. Never include credentials.

submit_feedback