Unwrap

Call after list_views to load the full Unwrap usage guide and color palette for the selected view. Recommended at the start of every MCP session, but the server is stateless and other tools work without it.

Get the authenticated org's view's. Returns view_id, view_name, and org_name for org's view's.

List the views connected feedback integrations and source coverage.

Search Unwrap's official product documentation (the public help center) and return a ranked list of matching article titles and URLs. Use this when the user asks how to do something in Unwrap, how a feature works, or how to set up or configure an integration. Pair with `read_documentation_article` to read an article's content before answering.

Read the full content of one or more Unwrap documentation articles and return them as markdown. Only URLs returned by `search_documentation` are allowed; any other URL is rejected without being fetched. Use this to ground answers to product, how-to, or integration-setup questions in the official docs.

Search for relevant segment fields and values by semantic similarity. Always call discover_filter_schema first to discover available fields before using this tool.

List exact allowed values for a segment. Use this before filtering when you need the precise value spelling.

List all available filters for a view. Returns every filter name that can be used for filtering. Use this at the start of the conversation to discover the available filters.

Find taxonomy groups via semantic search. If you filter, discover fields and values first instead of guessing them. For Entry Slug predicates use integer slug_id from sample_feedback_entries or classify_feedback_entries output (see discover_filter_schema).

Get the most actionable groups for the current question. Supports optional filters and optional numeric segment sorting. Use this for top groups or top issues queries, and often pair it with `plot_chart` when a visual summary would help.

Plot charts and tables over time or by breakdown. Use this when the user is asking about an issue or group over time, when they want top groups or top issues shown visually, or when a visual comparison would make the answer clearer. Choose the chart type based on whether the user wants a time trend, an aggregate ranking, or a share comparison. After calling it, still return written analysis alongside the chart. Use search_segments or list_field_values before filtering or selecting numeric segments.

Create a named sample of feedback entries. Use a representative random sample for prevalence, or semantic_query plus instruction for targeted examples. Slug names must be snake_case, 3-50 characters, lowercase letters, numbers, underscores only. MCP output includes slug_id at the end — pass it to analyze_entry_text, classify_feedback_entries, or Entry Slug filters on later calls.