Manage Ambush Feeds

Use the ambush-feeds MCP tools to turn plain-language monitoring requests into personalized news feeds and manage those feeds throughout their lifecycle.

Operating rules

• Verify that the Ambush Feeds MCP tools are available before acting. If they are unavailable, ask the user to connect the Ambush Feeds MCP server; do not substitute direct HTTP requests or ask for credentials.
• Use list_feeds to discover the user's feeds. Follow next_cursor only when the requested result may be on another page or the user asks for every feed.
• Use get_feed when the request needs the current prompt, delivery channels, usage, or recent emissions for one known feed.
• Resolve a feed by its returned ID. When names are duplicated or the target is ambiguous, present the matching names, prompts, and IDs and ask the user to choose.
• Never invent a feed ID, base-feed ID, cursor, prompt, status, emission, or tool result.
• Treat a missing feed name gracefully: identify it by a short prompt excerpt and its ID.
• If authentication is required, ask the user to connect or reauthenticate Ambush Feeds. Never ask the user to paste a bearer token.
• Report the result of every mutation, including the feed ID and returned status. Do not repeat a non-idempotent create call after an uncertain failure.

Create a feed