media_related_sessions
Find related media requests in the capture. Their presence is network evidence, not proof of playback.
tool · Connected client
Before you start
Capture the playlist and the player’s subsequent requests in the same run. Start from the media session ID you want to trace.
Access: Your MCP client needs the mediaSummary capability for this tool.
Request
{
"name": "media_related_sessions",
"arguments": {
"sessionID": "11111111-1111-4111-8111-111111111111"
}
} sessionID- Use the identifier of a retained test request, not the HTTP URL or a row number.
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
Find related media requests in the capture. Their presence is network evidence, not proof of playback.
If the result is unexpected
Repeat the app action inside the capture window if the expected segment is missing.
What to check if access is denied
Effects and cleanup
This request reads information; it does not start a test or activate a traffic change. Treat returned metadata and any exported evidence as potentially sensitive.
Same underlying tool: joesproxyctl media related.
Browse all MCP reference entries →