Easyparser — Amazon Product & Seller Data

get_bulk_job_items

Read-only

Inspect the individual items inside a bulk job: each item's input value (ASIN, keyword, seller ID...), its status (success/failed/invalid/pending/processing), error message if it failed, credit cost, and completion time.

Use this tool to debug a job after list_bulk_jobs shows failed_items or invalid_items > 0 — filter with status='failed' or status='invalid' to see exactly which inputs failed and why. Use search_key to locate one specific ASIN inside a large job. The item's item_id can be used with the Data Service (GET /v1/queries/{id}) to fetch its parsed result.

This tool is free of per-call credits (monitoring endpoints do not consume credits).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`page`	No	Page number. Default 1.
`limit`	No	Items per page (max 1000). Default 100.
`status`	No	Filter items by outcome. Use 'failed' or 'invalid' to debug a partial_success job; omit to see everything.
`date_to`	No	ISO date upper bound.
`group_id`	Yes	The job's group_id — get it from list_bulk_jobs (each job row has one). Identifies which job's items to inspect.
`date_from`	No	ISO date lower bound, e.g. 2026-08-01.
`search_key`	No	Search within item values (e.g. a specific ASIN) to find one item in a large job.
`sort_direction`	No	Sort by creation time. 'desc' (newest first) is default.	desc

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "description": "JSON response from the Easyparser Data Service or Account API. Non-object payloads are wrapped as { result }.",
+  "properties": {},
+  "type": "object"
+}

First observedSep 6, 2026

TDQS

Score is being calculated.

All Easyparser — Amazon Product & Seller Data 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.