Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

get_response_body

Retrieve the response body of a captured network request by request ID, so you can inspect returned content and debug API or page behavior.

Instructions

Get the response body of a captured network request

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "requestId": "<requestId>"
    },
    "name": "get_response_body"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabIdNoTab ID (optional)
requestIdYesRequest ID from network_requests output

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, yet it says nothing about whether the body is returned as text or base64, whether it may be truncated, or what happens when the body has been evicted or is unavailable. For a read tool that depends on prior capture state, this is a meaningful gap.

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

Conciseness4/5

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

A single, front-loaded sentence with no wasted words; it is easy to parse and gets to the point immediately. Brevity here is appropriate, though it borders on under-specification rather than optimal tightness.

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

Completeness3/5

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

For a simple two-parameter read tool with full schema coverage and no output schema, the description covers the core operation. It falls short on return-shape expectations (text vs. encoded body, truncation, missing-body behavior) that an agent would want before invoking it.

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 description coverage is 100%, and the schema already explains both tabId (optional) and requestId (from network_requests output). The description adds no format, encoding, or fallback semantics beyond that, so the baseline 3 applies.

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 uses a specific verb ("Get") and resource ("response body of a captured network request"), which makes the operation legible to an agent. It implicitly contrasts with network_requests (which lists requests) but never names it, so sibling differentiation is left to inference.

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

Usage Guidelines2/5

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

The description contains no explicit when-to-use or when-not-to-use guidance and names no alternative tool. The only routing hint, that requestId comes from network_requests output, lives in the schema rather than the description, so the definition itself supplies almost no usage context.

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