Skip to main content
Glama

get_response_body

Retrieve the response body of a network request by matching a substring in its URL, with optional HTTP method filter. Use to diagnose server errors without prior setup.

Instructions

Return the captured response body text for a request whose URL contains a substring (optionally filtered by method). Matching is a plain substring test against the full URL incl. query string — not a regex or glob. On a miss it lists the captured candidate URLs so you can adjust the pattern in one round-trip. Bodies are captured automatically for fetch/xhr/document requests, making this the fastest way to diagnose a 400/500 — no setup before the request.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
methodNoHTTP method filter (optional, e.g. 'POST', 'GET')
session_idYesSession ID
url_patternYesPlain substring of the full URL incl. query string (e.g. '/api/quotes', 'graphql') — not a regex; anchors ($) and wildcards (.*) never match.
Behavior4/5

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

Given no annotations, the description discloses that matching is a plain substring test (not regex), explains miss behavior, and clarifies that bodies are automatically captured. It does not mention potential performance or size limits, but is otherwise transparent.

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 concise with four sentences, each serving a purpose: purpose, matching rule, miss behavior, and use case. No extraneous text; front-loaded with the core function.

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

Completeness4/5

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

The description covers the core functionality, matching semantics, and error recovery. It lacks details about return format (though implied) and does not mention session prerequisites, but these are reasonable omissions given the tool's simplicity.

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

Parameters4/5

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

All three parameters are described in the schema (100% coverage). The description adds valuable context beyond schema: url_pattern is not regex, includes examples, and explains method is optional. This enhances understanding.

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 it returns captured response body text given a URL substring and optional method filter. It distinguishes from siblings by noting it's the fastest way to diagnose 400/500 errors with no setup, but does not explicitly differentiate from get_network_log or similar tools.

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

Usage Guidelines4/5

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

The description implies use for debugging HTTP errors and provides guidance on adjusting patterns when a miss occurs. However, it does not explicitly state when not to use or list alternatives.

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/segentic-lab/periscope-mcp'

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