get_playbook_input

Inputs

{
  "type": "object",
  "properties": {
    "playbook": {
      "type": "string",
      "enum": [
        "outlier-posts",
        "transcript-intel",
        "comment-mining",
        "creator-teardown",
        "repurpose-pack"
      ]
    },
    "arguments": {
      "type": "object",
      "description": "The selected playbook's prompt arguments, with string values. Pass video_ids and kinds as comma-separated strings."
    }
  },
  "additionalProperties": false,
  "required": [
    "playbook",
    "arguments"
  ]
}

Outputs and behavior

Prepare cited local evidence and instructions for a client-written research report. Use for creator comparisons, transcript analysis, comment mining or repurposing; use analyze_self_channel for computed own-channel performance, search_library for ad hoc retrieval and get_library_brief_input for a dated operational brief. Returns instruction, packet and packet_hash within the library read budget. The client does the analysis; no model is called. Argument selectors depend on the selected playbook.

The registry does not publish an output schema for this tool. The description above is its documented behavior; response fields beyond it are not specified here.

Example call

Example tool name and arguments, generated from the input schema. Replace placeholder strings and sample numbers with your own values. This is a request template, not a recorded call or response.

{
  "name": "get_playbook_input",
  "arguments": {
    "playbook": "outlier-posts",
    "arguments": {}
  }
}

Clients

This tool is available to MCP clients using stdio or http.

The registry records transport support, not individual client test results. See the MCP setup reference for named clients, configuration, and tool-list limits.