Easyparser — Amazon Product & Seller Data

list_bulk_jobs

Read-only

List the user's bulk extraction jobs with their progress: operation, domain, status, total/completed/failed/invalid item counts, and timestamps. This reads the SAME data as the Bulk Requests page in the Easyparser web app — so it can see and track jobs the user started from the app UI, not just jobs submitted through this MCP server.

Use this tool when the user asks about their bulk jobs: "is my job done?", "what bulk jobs are running?", "did the DETAIL batch finish?". Each row includes a group_id — pass it to get_bulk_job_items to drill into individual items, or to get_bulk_webhook_logs to check webhook deliveries.

Statuses: pending (queued), processing (running), completed (all items succeeded), partial_success (some items failed or were dropped — check failed_items/invalid_items counts), failed. This tool is free of per-call credits (monitoring endpoints do not consume credits).

Input Schema

Name	Required	Description	Default
`page`	No	Page number. Default 1.
`limit`	No	Items per page (max 1000). Default 100.
`domain`	No	Filter by marketplace domain.
`status`	No	Filter by job status: pending, processing, completed, partial_success (some items failed), failed.
`operation`	No	Filter by operation type, e.g. DETAIL or SEARCH.
`sort_direction`	No	Sort by creation time. 'desc' (newest first) is default.	desc
`bulk_request_id`	No	Look up a specific job by its bulk_request_id (returned when the job was submitted).

Output 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

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so safety is covered. The description adds non-obvious behavioral facts: it reads web-app jobs too, it is free of per-call credits (rate/cost behavior), and it explains each status including partial_success semantics ('some items failed or were dropped'). It doesn't detail pagination behavior, which keeps it from a 5.

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?

Front-loads the core purpose in the first clause, then usage, routing, status legend, and cost note in a logical order. Every sentence (status definitions, credit note, sibling routing) carries information an agent needs; nothing is padding.

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 7-param read-only list tool with an output schema and 100% schema coverage, this is complete: purpose, when to use, sibling routing, status semantics, and cost behavior are all covered, with the output schema handling return shape.

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 baseline is 3. The description compensates for the implicit filter semantics by describing statuses in prose (pending=queued, processing=running, partial_success=partial) and referencing group_id as a drill-down key, adding meaning beyond the enum labels. Pagination/page-limit syntax is left to 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 (bulk extraction jobs), and the exact fields returned (operation, domain, status, counts, timestamps). It also distinguishes itself from sibling listers by noting it reads the same data as the web UI, so it covers app-started jobs — something no sibling (get_bulk_job_items, get_bulk_webhook_logs) does.

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 names when to use it with real user phrasings ('is my job done?', 'what bulk jobs are running?') and routes to siblings: pass group_id to get_bulk_job_items or get_bulk_webhook_logs. That is explicit when-to-use plus named alternatives.

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

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.