Customer Interview Kit
customer_interview_kitGenerate a tailored customer interview guide and synthesis templates from your interview type, product context, and target persona, so you know exactly what to ask before conducting research interviews.
Instructions
Helps you decide what to ask customers to test your hunch: it takes the interview type, the product context and the person you are interviewing, and returns an interview guide that fits the interview type, the sector and the product complexity. Questions use the sector's own language (the sector is chosen, or read from your inputs), your hypotheses are kept whole, and synthesis templates are included. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of icp_interview_synthesizer when you need questions and synthesis templates before conducting interviews.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"interview_type": "<interview_type>",
"product_context": "<product_context>",
"target_persona": "<target_persona>"
},
"name": "customer_interview_kit"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| industry | No | Industry affects terminology and context. Leave it out and the sector is read from your other inputs. Format is text using one of the listed labels. For example, "saas". | |
| your_sector | No | Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear. Format is text using one of the listed labels. For example, "logistics_tech". | |
| business_model | No | Optional: how you earn revenue, so the advice fits it (saas, services, connectivity, transactions, marketplace, hardware_software or investment). Leave it out and the tool reads it from your other inputs and says how it read it. Format is text using one of the listed labels. For example, "saas". | |
| interview_type | Yes | Type of interview determines question focus. Format is text using one of the listed labels. For example, "discovery". | |
| key_hypotheses | No | Optional: Hypotheses to validate during interview, one per line or separated by semicolons. Format is text. For example, "confirm who approves invoice exceptions". | |
| target_persona | Yes | Who you're interviewing (role/title). Format is text. For example, "finance director". | |
| product_context | Yes | Product/service being researched. Format is text. For example, "checks invoice exceptions before approval". | |
| product_complexity | No | Affects technical depth of questions. Format is text using one of the listed labels. For example, "simple". |