audience_get_filters

com.youricp/mcp-server · Verify this server

Fetch all available audience filter categories as an interactive filter picker. Only call this after audience_start has been called and the user chose Option B (interactive filter picker). Do not call this tool to guess or pre-populate filters on behalf of the user. RENDERING — MANDATORY, VERBATIM: The response is usually a complete HTML document. Pass the returned HTML string unchanged to the visualizer/render tool. Do NOT rebuild, restyle, summarize, trim, or hand-author a replacement UI. If the response is plain text instead of an HTML document (this happens on clients that cannot render HTML), simply present that text to the user as-is and let them pick filter values by name — do not look for a visualizer. Render EVERY tab and EVERY chip exactly as received, in the order received, using the exact data-cat and data-val attributes the backend emitted. This includes tabs whose chip list is empty — render the empty tab as-is, do NOT drop it and do NOT invent or backfill chips for it. ALWAYS keep the "Get estimation" button (id="getEstBtn") in the rendered widget. It is the action control the user clicks to run the preview — never remove, hide, rename, or replace it. Do NOT move a chip from the tab/category the backend placed it in. If a value arrives under data-cat="industries", it is rendered and reported under industries — the client must not re-route it to seniority, departments, buying_roles, employee_size, or revenue based on its label. Field placement is the backend's responsibility, not the client's. When the user makes selections, resolve names→keys ONLY via the <script id="filter-key-map"> JSON in the returned HTML, then call audience_preview with those exact keys.