Skip to main content
Glama

proxy_replay_session

Replay filtered requests from a recorded HTTP session. Use dry_run to preview the replay plan before executing, with controls for method, URL, time range, and target base URL override.

Instructions

Replay selected requests from a recorded/imported session. Default mode is dry_run for safety.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNodry_run previews replay plan; execute sends the requestsdry_run
sortNodesc
textNoGeneric text filter
limitNo
to_tsNoUnix ms upper-bound timestamp
methodNoHTTP method filter
offsetNo
from_tsNoUnix ms lower-bound timestamp
session_idYesSession ID
timeout_msNoPer-request timeout in milliseconds
status_codeNoResponse status code filter
exchange_idsNoExplicit exchange IDs to replay (overrides query filters)
url_containsNoFilter by URL substring
target_base_urlNoOptional base URL override (keeps original path+query)
hostname_containsNoFilter by hostname substring
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden. It reveals that dry_run is safe and execute sends requests, but lacks details on permissions, reversibility, or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with core action (replay) and key default (dry_run). No extraneous words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite 15 parameters, the description is very brief. It does not explain what dry_run returns, how filters interact, or expected output format. Lacks completeness for a complex tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 80%, so the baseline is 3. The description adds no extra meaning to parameters beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (replay) and resource (requests from a session). It is distinct from sibling tools like proxy_export_har, but does not explicitly differentiate itself.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage with dry_run for safety, but offers no guidance on when to use this tool over alternatives like proxy_query_session or proxy_get_session_exchange.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yfe404/proxy-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server