Skip to main content
Glama
Internamaro Apify Data MCP

Internamaro Apify Data MCP

Bulk HTTP Request

bulk_http_request

Send many HTTP requests in parallel with retries and get per-request status, headers, body, timing, and error details.

Instructions

Returns one item per request with URL, method, status code, selected response headers, JSON or text body, timing and error. Sends many HTTP requests (GET, POST, PUT, PATCH, DELETE, HEAD with your headers and body) in parallel with retries. Requests to internal or private addresses are blocked. Give at least one of: requests or urls. Runs the Apify Actor ucchiii/bulk-http-request on YOUR Apify account (APIFY_TOKEN); you pay that Actor's pay-per-event price, see https://apify.com/ucchiii/bulk-http-request.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bulk_http_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoOptional request body for the simple URL list and for items without their own body. Sent as text; if it is valid JSON and you set no Content-Type, it is sent as application/json.
urlsNoOptional shortcut: plain URLs that are all sent with the shared method, headers and body below. Added after the requests above.
methodNoHTTP method for the simple URL list, and for request items that do not set their own.GET
headersNoOptional headers sent with every request, for example {"Authorization": "Bearer ..."}. Values such as Authorization and Cookie are never written to logs and are shown as [REDACTED] in the output. Use your own credentials only; they are part of the run input, so keep the run private.
retriesNoHow many times a failed request is retried (connection errors and timeouts; HTTP 429/502/503/504 for GET, HEAD, PUT and DELETE). POST and PATCH are retried only when no connection could be made, so nothing is sent twice. Retries are not charged.
requestsNoList of requests to send. Each item is an object with url (required), method (GET, POST, PUT, PATCH, DELETE or HEAD), headers (object) and body (string, or any JSON value that is sent as JSON). Missing method, headers and body fall back to the shared settings below.
parseJsonNoIf on, a complete response body that is valid JSON is returned as the json field (and body is left empty). Otherwise the body is returned as text.
concurrencyNoHow many requests are in flight at the same time (1 to 20). At most 5 connections per host are used at a time.
timeoutSecsNoTimeout for each request attempt.
maxBodyBytesNoResponse bodies longer than this are cut off and bodyTruncated is set to true. 100000 is about 100 KB; 0 stores no body.
followRedirectsNoFollow redirects (up to 10). Every hop is checked against the internal-address block. Authorization and Cookie headers are dropped when a redirect goes to another host.
responseHeadersNoWhich response headers to include in the output. Set-Cookie and similar secret headers are always shown as [REDACTED].selected

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only mark this non-read-only and open-world; the description adds substantial behavior: parallel execution limits via retries semantics, SSRF blocking of private addresses, credential redaction in logs and output, redirect hops re-checked and Authorization/Cookie dropped cross-host, and body truncation. It also discloses the billing model (pay-per-event price on your own Apify account) and a privacy warning about credentials in run input — none of which the annotations convey.

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?

It is front-loaded with the return shape and the core action, then layers constraints, pricing and prerequisites. Dense and mostly waste-free, though the actor URL and billing sentence could be compressed.

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?

With no output schema, the description carries return-value disclosure and does so (per-request fields including status, headers, body, timing, error). For a 12-parameter, nested-object network tool it covers the operational facts an agent needs: auth, parallel limits, blocking rules, truncation and cost.

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?

Schema coverage is 100%, so a 3 is the baseline. The description exceeds that by surfacing the cross-parameter constraint that at least one of requests/urls must be supplied — a rule not visible from the empty required array — and by describing how per-request fields fall back to shared settings.

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?

The description names the specific verb and resource ('Sends many HTTP requests ... in parallel with retries') and enumerates supported methods (GET, POST, PUT, PATCH, DELETE, HEAD). It also states the return shape ('one item per request with URL, method, status code, selected response headers, JSON or text body, timing and error'), so an agent can tell this is a parallel bulk-fetching tool, distinct from the JSON/table utility siblings.

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?

It gives an explicit input precondition ('Give at least one of: requests or urls') and a hard exclusion ('Requests to internal or private addresses are blocked'), plus an environment prerequisite (runs on YOUR Apify account with APIFY_TOKEN). It does not name alternative tools for simpler single-request needs, but none of the listed siblings are substitutes for HTTP fetching.

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