Samplecut

{
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "url",
    "context",
    "llm_model"
  ],
  "properties": {
    "url": {
      "type": "string",
      "maxLength": 2048,
      "minLength": 1,
      "description": "YouTube, TikTok, Instagram, or SoundCloud URL to fetch captions for"
    },
    "lang": {
      "type": "string",
      "maxLength": 32,
      "minLength": 1,
      "description": "Optional BCP-47 caption language (default en)"
    },
    "context": {
      "type": "string",
      "description": "One short sentence on what the user is trying to do with this audio (for example 'ringtone from the chorus'). No links, names or personal details."
    },
    "llm_model": {
      "type": "string",
      "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess."
    },
    "conversation_id": {
      "type": "string",
      "description": "Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request."
    }
  }
}

{
  "type": "object",
  "required": [
    "feedback_type",
    "summary",
    "llm_model"
  ],
  "properties": {
    "details": {
      "type": "string",
      "description": "Optional longer context: what you tried, exact parameter values, the error text you saw, and any workaround you used. Omit when the summary says it all."
    },
    "summary": {
      "type": "string",
      "description": "One self-contained sentence. For 'missing_capability': the capability you needed, e.g. 'No tool to delete multiple cohorts in one call.' For 'issue': the tool and the problem, e.g. 'query-trends rejects relative date ranges with an unclear error.'"
    },
    "llm_model": {
      "type": "string",
      "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess."
    },
    "sentiment": {
      "enum": [
        "positive",
        "neutral",
        "negative",
        "mixed"
      ],
      "type": "string",
      "description": "Optional: how the experience felt overall."
    },
    "tool_name": {
      "type": "string",
      "description": "Optional: the existing tool this feedback is about (for 'issue' or 'praise'). Leave empty for 'missing_capability' - the point is that no tool fits."
    },
    "feedback_type": {
      "enum": [
        "missing_capability",
        "issue",
        "praise",
        "other"
      ],
      "type": "string",
      "description": "What kind of feedback this is. Use 'missing_capability' when the tool you needed does not exist in the tool list - nothing failed, the capability is absent (this is the most valuable report; send it even if you found a workaround). Use 'issue' when an existing tool behaved badly: it failed, returned a confusing error, or its description or schema misled you. Use 'praise' when something worked notably well. Use 'other' for anything else."
    },
    "task_completed": {
      "type": "boolean",
      "description": "Optional: whether you still completed the user's task despite the problem."
    },
    "conversation_id": {
      "type": "string",
      "description": "Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request."
    },
    "friction_points": {
      "type": "string",
      "description": "Optional: the specific moments that slowed you down, as short bullet-like sentences, quoting exact tool names, parameters, or error text."
    },
    "suggested_improvement": {
      "type": "string",
      "description": "Optional: the concrete change that would have helped, e.g. the tool to add, the description to reword, or the error message to improve."
    }
  }
}