hls_fixture_stop · JoesProxy

tool · Connected client

Before you start

Find the run in fixture status using the client that started it. Match its run ID before stopping it; a profile ID identifies a recipe, not a running stream.

Access: Your MCP client needs the hlsFixtureLifecycle capability for this tool.

Request

{
  "name": "hls_fixture_stop",
  "arguments": {
    "runID": "11111111-1111-4111-8111-111111111111"
  }
}

runID: Use an owned fixture run ID, not a profile name.

Illustrative tools/call parameters. Inspect the tool’s inputSchema in tools/list before sending them. Replace the synthetic UUID with the identifier from your own authorized session.

What to look for

Stop the owned fixture run and unregister its local fixture origin.

If the result is unexpected

Use the run ID, not the profile ID. Confirm status after stopping.

What to check if access is denied

Effects and cleanup

Work on your own fixture and test client. Stop the fixture after the comparison and verify that later requests use the original stream.

Same underlying tool: joesproxyctl hls fixture stop.

Browse all MCP reference entries →