URLpipe

List past requests

list_requests

Read-onlyIdempotent

A project's recent requests, newest first, with each one's token.

Look here before fetching a page: if somebody already pulled it, passing that token to get_result returns the same result for nothing. A /scrape appears as one entry — its per-operation children are internal, and the scrape's own token returns all of them.

Pass labels to see only the requests made with them — every key given must match its value exactly.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	No	Only requests for this exact URL.
`limit`	No	How many to return. Default 25, maximum 100.
`labels`	No	Only requests made with all of these labels, each value matched exactly.
`offset`	No	Skip this many, for paging.
`operation`	No	Only requests running this operation.
`project_id`	Yes	From list_projects.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`total`	Yes
`offset`	Yes
`requests`	Yes
`project_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 25, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "properties": {
+    "offset": {
+      "type": "integer"
+    },
+    "project_id": {
+      "type": "integer"
+    },
+    "requests": {
+      "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"
+    },
+    "total": {
+      "type": "integer"
+    }
+  },
+  "required": [
+    "project_id",
+    "total",
+    "offset",
+    "requests"
+  ],
+  "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 declare readOnly, idempotent, and non-destructive, so the description need not restate those. It adds useful behavioral nuance: /scrape appears as one entry with internal children, and the scrape token aggregates them. Also notes exact label matching. No contradictions.

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?

Three concise sentences front-load the core purpose and ordering, then add critical behavioral and filtering details without fluff. Every sentence earns its place.

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?

For a list tool with 6 parameters, an output schema, and rich annotations, the description covers ordering, token reuse, scrape aggregation, and label matching. Pagination is handled by schema; return structure is in output schema. Nothing essential 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 coverage is 100%, so parameters are already described. The description reinforces the labels parameter ('every key given must match its value exactly') but adds little beyond schema. No additional syntax or edge cases beyond what's in the schema.

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 (list), resource (requests of a project), and ordering (newest first) with tokens. Clearly distinguishes from get_request and get_result by focusing on the listing of past requests and the token reuse.

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?

Explicitly instructs to look here before fetching a page, explaining that passing a token to get_result reuses cached results. Also clarifies the /scrape entry behavior and label filtering, giving concrete when-to-use guidance.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?