Bulk User-Agent Parser
bulk_parse_user_agentParse up to 250 user-agent strings in one request and return structured browser, device, engine, and OS details.
Instructions
Read-only bulk user-agent parsing via POST /v3/user-agent-bulk. Paid only. Cost: 1 credit per successful string. This MCP server accepts up to 250 explicit user-agent strings. Larger batches are rejected before any API call. Complete results within upstream and cache byte limits are returned directly or as cached pages. Cached pages use get_cached_result without another API call or additional credits. An upstream body above its byte limit, or a required pagination snapshot too large to retain, returns a non-retryable resource_limit error with no cursor; the API may already have used credits.
Returns one parsed object per string with user_agent_string, name, type, version, version_major, device, engine, and operating_system. uaStrings must be a non-empty array of exact user-agent strings; empty/null strings are rejected locally before any API call. parse_user_agent handles a single string. force_refresh bypasses cached data, makes a new upstream request, and can consume credits.
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": {
"uaStrings": "<uaStrings>"
},
"name": "bulk_parse_user_agent"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| uaStrings | Yes | Array of user-agent strings to parse. Minimum 1, maximum 250 in this MCP server. | |
| force_refresh | No | Default false. When true, bypasses cached bulk user-agent parsing data; a successful refresh makes a new upstream request and can consume credits. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| error | No | Present when the whole tool call fails, with isError: true. | |
| items | No | Present on success: complete API results in input order, including any per-item error messages. | |
| errors | No |