Skip to main content
Glama

web-api-mcp

Collect queued requests

check_requests
Read-only

Collect requests the API is running in the background.

Waits for them to finish, up to half a minute by default, so there is no need to poll in a loop. Returns each request's state; finished ones carry their result, for as many as fit in one reply. The rest come as summaries marked summarized, holding as much of each page as there was room for: read on with read_result. A parser note comes once, in parser_notes, and each result names its own. Only the first few screenshots come back as images. If some are still pending, call again with only their request ids.

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": {
      "request_ids": "<request_ids>"
    },
    "name": "check_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idsYesThe `request_id`s of queued requests, from `scrape` or `run_scraper` replies or an earlier call to this tool. A single id is fine.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.