URLpipe

Inspect a past request

get_request

Read-onlyIdempotent

Everything about one past request except its result: what was asked for, how long each stage took, whether it came from the store, and how the webhook delivery went.

This is the metadata; get_result returns the page itself. Reach for this one when a call did not do what you expected — it says whether the result was reused, why an analysis failed, and whether the delivery to the project's endpoint succeeded.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`token`	Yes	The token the original call returned.
`project_id`	Yes	From list_projects.

Output Schema

TableJSON Schema

Name	Required	Description
`url`	Yes
`meta`	No	What the HTTP response headers would say: cache, cost, quota, result_url, final_url.
`async`	No
`token`	Yes
`labels`	No
`status`	Yes
`credits`	No
`max_age`	No
`outcome`	No
`success`	No
`final_url`	No	Where the page ended up after its redirects.
`operation`	No
`report_to`	No
`created_at`	No
`operations`	No
`duration_ms`	No
`finished_at`	No
`webhook_error`	No
`webhook_status`	No
`request_options`	No
`served_from_cache`	No
`webhook_delivered_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 30, 2026

addedOutput schema / properties / final_url

Added value: +{
+  "description": "Where the page ended up after its redirects.",
+  "type": "string"
+}

changedOutput schema / properties / meta / description

Previous value: -"What the HTTP response headers would say: cache, cost, quota, result_url."New value: +"What the HTTP response headers would say: cache, cost, quota, result_url, final_url."

addedOutput schema / properties / operations / items / properties / final_url

Added value: +{
+  "description": "Where the page ended up after its redirects.",
+  "type": "string"
+}

Changed1 schema field changedSep 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "properties": {
+    "async": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "created_at": {
+      "type": "string"
+    },
+    "credits": {
+      "type": "integer"
+    },
+    "duration_ms": {
+      "type": "integer"
+    },
+    "finished_at": {
+      "type": "string"
+    },
+    "labels": {
+      "additionalProperties": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "max_age": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "meta": {
+      "description": "What the HTTP response headers would say: cache, cost, quota, result_url.",
+      "type": "object"
+    },
+    "operation": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "operations": {
+      "items": {
+        "properties": {
+          "created_at": {
+            "type": "string"
+          },
+          "credits": {
+            "type": "integer"
+          },
+          "duration_ms": {
+            "type": "integer"
+          },
+          "finished_at": {
+            "type": "string"
+          },
+          "labels": {
+            "additionalProperties": {
+              "type": "string"
+            },
+            "type": "object"
+          },
+          "operation": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "served_from_cache": {
+            "type": [
+              "boolean",
+              "null"
+            ]
+          },
+          "status": {
+            "type": "string"
+          },
+          "success": {
+            "type": [
+              "boolean",
+              "null"
+            ]
+          },
+          "token": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "token",
+          "url",
+          "status"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "outcome": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "report_to": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "request_options": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "served_from_cache": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "status": {
+      "type": "string"
+    },
+    "success": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "token": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    },
+    "webhook_delivered_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "webhook_error": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "webhook_status": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "token",
+    "url",
+    "status"
+  ],
+  "type": "object"
+}

First observedSep 25, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already establish readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuine behavioral value beyond that: it reveals what data is exposed (stage timings, store reuse, webhook delivery outcome, why an analysis failed) and what is excluded (the result). It stops short of stating auth or rate-limit behavior, but for a read tool that is a minor gap.

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?

Two tight sentences, both front-loaded with the key constraint (result excluded) and the decision trigger. No filler; every clause carries information.

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

Completeness5/5

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

An output schema exists, so return-shape explanation is not required, yet the description still tells the agent which diagnostic fields to expect and why to call it. Nothing an agent needs to invoke it correctly is missing.

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 both parameters are documented in the schema (token, project_id with source hint). The description adds no further parameter syntax or semantics, so baseline 3 applies.

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

Purpose5/5

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

States a specific verb (inspect) and resource (one past request) and immediately delimits scope: 'Everything about one past request except its result.' It explicitly separates itself from get_result, so an agent can route without opening either schema.

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

Usage Guidelines5/5

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

Gives an explicit when-to-use trigger ('Reach for this one when a call did not do what you expected') and names the alternative (get_result returns the page itself). The contrast with the sibling makes the selection condition unambiguous.

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

All URLpipe tools Inspect

Try in Browser

Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?