get_traffic_entry_detail
Retrieve detailed network traffic data for inspection by providing an entry ID from Charles Proxy summaries, enabling drill-down analysis of specific HTTP requests and responses.
Instructions
Load one traffic entry detail view for drill-down inspection. Requires entry_id from a prior summary/query call. For history entries, pass recording_path from the summary. For live entries, pass capture_id from the summary. Keep include_full_body=false unless you specifically need the raw body text.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| source | Yes | ||
| entry_id | Yes | ||
| capture_id | No | ||
| recording_path | No | ||
| include_full_body | No | ||
| max_body_chars | No |
Implementation Reference
- charles_mcp/tools/history.py:96-118 (handler)The tool 'get_traffic_entry_detail' is defined as an async function decorated with '@mcp.tool()'. It uses 'traffic_query_service' from the dependencies to fetch the details of a traffic entry based on the provided parameters.
async def get_traffic_entry_detail( ctx: ToolContext, source: str, entry_id: str, capture_id: Optional[str] = None, recording_path: Optional[str] = None, include_full_body: bool = False, max_body_chars: int = 2048, ) -> TrafficDetailResult: """Load one traffic entry detail view for drill-down inspection. Requires entry_id from a prior summary/query call. For history entries, pass recording_path from the summary. For live entries, pass capture_id from the summary. Keep include_full_body=false unless you specifically need the raw body text.""" deps = get_tool_dependencies(ctx) return await deps.traffic_query_service.get_detail( source=source, entry_id=entry_id, capture_id=capture_id, recording_path=recording_path, include_full_body=include_full_body, max_body_chars=max_body_chars, )