Skip to main content
Glama

AIsa Shopping & Marketplace

by one.aisa
OverviewDiscussionsAdmin

Get Amazon Sellers HTML Results by id

get_dataforseo_merchant_amazon_sellers_fetch_html
Read-onlyIdempotent

Description of the fields for sending a request:

Published reference price: $0 USD per successful request. Account-specific pricing and final settlement may differ.

Input Schema

NameRequiredDescriptionDefault
idYes<em>task identifier</em><br><strong>unique task identifier in our system in the <a href="https://en.wikipedia.org/wiki/Universally_unique_identifier">UUID</a> format</strong><br>you will be able to use it within <strong>7 days</strong> to request the results of the task at any time

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"task identifier unique task identifier in our system in the UUID format you will be able to use it within 7 days to request the results of the task at any time"New value: +"<em>task identifier</em><br><strong>unique task identifier in our system in the <a href=\"https://en.wikipedia.org/wiki/Universally_unique_identifier\">UUID</a> format</strong><br>you will be able to use it within <strong>7 days</strong> to request the results of the task at any time"
    • addedInput schema / properties / id / example
      Added value: +"00000000-0000-0000-0000-000000000000"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  2. Changed3 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"<em>task identifier</em><br><strong>unique task identifier in our system in the <a href=\"https://en.wikipedia.org/wiki/Universally_unique_identifier\">UUID</a> format</strong><br>you will be able to use it within <strong>7 days</strong> to request the results of the task at any time"New value: +"task identifier unique task identifier in our system in the UUID format you will be able to use it within 7 days to request the results of the task at any time"
    • removedInput schema / properties / id / example
      Removed value: -"00000000-0000-0000-0000-000000000000"
    • removedOutput schema / x-fastmcp-wrap-result
      Removed value: -true
  3. Changed3 schema fields changed
    • changedInput schema / properties / id / description
      Previous value: -"task identifier unique task identifier in our system in the UUID format you will be able to use it within 7 days to request the results of the task at any time"New value: +"<em>task identifier</em><br><strong>unique task identifier in our system in the <a href=\"https://en.wikipedia.org/wiki/Universally_unique_identifier\">UUID</a> format</strong><br>you will be able to use it within <strong>7 days</strong> to request the results of the task at any time"
    • addedInput schema / properties / id / example
      Added value: +"00000000-0000-0000-0000-000000000000"
    • addedOutput schema / x-fastmcp-wrap-result
      Added value: +true
  4. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"DataForSEO task ID."New value: +"task identifier unique task identifier in our system in the UUID format you will be able to use it within 7 days to request the results of the task at any time"
  5. First observed

TDQS

D1.6/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds only a pricing disclaimer, which is marginally useful but discloses nothing about the retrieval behavior, the id's 7-day window, or error cases.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short, but the brevity comes from omission rather than efficiency. The lead sentence is filler and the pricing comment block is the only substantive content, so no sentence actually explains the tool's use.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has an output schema, so return values need not be explained, but the description still omits purpose, usage, and any distinction from the non-HTML sibling. For a fetch-by-id tool in a large family, this is inadequate.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With one parameter and 100% schema description coverage, the schema already explains that the id is a UUID and is usable for 7 days. The description contributes no additional parameter semantics, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description body never states what the tool does; it only says 'Description of the fields for sending a request' plus a pricing note. The actual purpose (retrieving stored Amazon Sellers HTML task results by id) is inferable only from the name and title, not from the description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, no mention of the retrieval step after submit, and no differentiation from the sibling get_dataforseo_merchant_amazon_sellers_fetch (non-HTML variant). The agent gets nothing to route on.

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

All AIsa Shopping & Marketplace toolsInspect
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.

Resources