post_dataforseo_merchant_amazon_asin_submitThis endpoint will provide you with a full list of ASINs assigned to different modifications of a product.
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Input schema / properties / body / items / properties / language_code / descriptionPrevious value: -"search engine language code required field if you don’t specify language_name if you use this field, you don’t need to specify language_name you can receive the list of available languages with their language_code parameters by making a separate request to the https://api.dataforseo.com/v3/merchant/amazon/languages example: en_GB"New value: +"search engine language code required field if you don't specify language_name if you use this field, you don't need to specify language_name you can receive the list of available languages with their language_code_parameters by making a separate request to the https://api.dataforseo.com/v3/merchant/amazon/languages example: en_GB"Input schema / properties / body / items / properties / location_code / descriptionPrevious value: -"search engine location code required field if you don’t specify location_name or location_coordinate if you use this field, you don’t need to specify location_name or location_coordinate you can receive the list of available locations with their location_code parameters by making a separate request to the https://api.dataforseo.com/v3/merchant/amazon/locations example: 9045969"New value: +"search engine location code required field if you don't specify location_name_or location_coordinate if you use this field, you don't need to specify location_name or location_coordinate you can receive the list of available locations with their location_code parameters by making a separate request to the https://api.dataforseo.com/v3/merchant/amazon/locations example: 9045969n"Input schema / properties / body / items / properties / location_coordinate / descriptionPrevious value: -"GPS coordinates of a location required field if you don’t specify location_name or location_code if you use this field, you don’t need to specify location_name or location_code location_coordinate parameter should be specified in the “latitude,longitude,radius” format the maximum number of decimal digits for “latitude” and “longitude”: 7 the minimum value for “radius”: 199.9 example: 53.476225,-2.243572,200"New value: +"GPS coordinates of a location required field if you don't specify location_name_or location_code if you use this field, you don't need to specify location_name or location_code location_coordinate parameter should be specified in the \"latitude,longitude,radius\" format the maximum number of decimal digits for \"latitude\" and \"longitude\": 7 the minimum value for \"radius\": 199.9 example: 53.476225,-2.243572,200"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description implies a read-style list delivery, while the annotations declare readOnlyHint=false, destructiveHint=true and idempotentHint=false. It says nothing about task creation, the extra charge for high-priority tasks, postback/pingback notification behavior, or that repeated calls create new tasks — all behaviors the annotations suggest but the text omits or contradicts.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One short sentence with a single clause, so it is structurally efficient and front-loaded. Conciseness is fine, but the single sentence is spent on the wrong content, so it earns only partial credit.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a non-idempotent, destructive, open-world task-submission endpoint taking a required ASIN plus location/language, the description supplies none of the operational context an agent needs (submission vs. retrieval, cost, notification callbacks). An output schema exists but does not excuse omitting the write semantics.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description never mentions the body array or any of its members (asin required; one of location_name/location_code/location_coordinate; one of language_name/language_code). Reported schema description coverage is 0% at the top level, so the description was obligated to compensate and does not; it only adds zero parameter meaning beyond the schema's own nested field descriptions.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description reads like a retrieval endpoint ('will provide you with a full list of ASINs') even though the tool's name and its post_dataforseo_merchant_amazon_asin_fetch sibling show this is a task-submission call. The resource (Amazon ASIN data) is named, but the action is never identified, so an agent cannot tell what the call actually does.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this versus post_dataforseo_merchant_amazon_products_submit or get_dataforseo_merchant_amazon_asin_fetch, and no mention of the submit-then-fetch asynchronous pattern implied by the sibling set. The reader is left to infer usage entirely from the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.