Skip to main content
Glama
Decodo

Decodo MCP Server

amazon_sellers

Read-only

Scrape Amazon seller data by providing a seller ID. Supports custom domains, device types, and geolocation for tailored results.

Instructions

Scrape Amazon Seller information with automatic parsing

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesAmazon seller ID (e.g., "A1R0Z7FJGTKESH")
jsRenderNoShould the request be opened in a headless browser, false by default
domainNoAmazon domain (e.g., amazon.com, amazon.co.uk)
deviceTypeNoDevice type to emulate for the request
geoNoAmazon geo location (e.g., 10001 for US ZIP code)

Implementation Reference

  • The AmazonSellersTool class that implements the tool logic. The register method (lines 25-61) registers the 'amazon_sellers' tool with the MCP server, handling the scraping of Amazon seller information by calling sapiClient.scrape with target 'amazon_sellers'.
    export class AmazonSellersTool extends Tool {
      toolset = TOOLSET.ECOMMERCE;
    
      transformResponse = ({ data }: { data: object }) => {
        return { data: JSON.stringify(data) };
      };
    
      register = ({ server, sapiClient, auth }: ToolRegistrationArgs) => {
        server.registerTool(
          'amazon_sellers',
          {
            description: 'Scrape Amazon Seller information with automatic parsing',
            inputSchema: {
              query: z.string().describe('Amazon seller ID (e.g., "A1R0Z7FJGTKESH")'),
              jsRender: zodJsRender,
              domain: zodDomain,
              deviceType: zodDeviceType,
              geo: zodGeo,
            },
            annotations: {
              readOnlyHint: true,
              openWorldHint: true,
            },
          },
          async (scrapingParams: ScrapingMCPParams, extra: ProgressExtra) => {
            const params = {
              ...scrapingParams,
              target: SCRAPER_API_TARGETS.AMAZON_SELLERS,
              parse: true,
            } satisfies ScraperAPIParams;
    
            const { data } = await sapiClient.scrape<object>({ auth, scrapingParams: params, extra });
    
            return {
              content: [
                {
                  type: 'text',
                  text: JSON.stringify(data),
                },
              ],
            };
          }
        );
      };
    }
  • Zod schemas for the tool's input parameters: zodDomain (Amazon domain, optional) and zodGeo (Amazon geo location, optional).
    const zodDomain = z
      .string()
      .describe('Amazon domain (e.g., amazon.com, amazon.co.uk)')
      .optional();
    
    const zodGeo = z
      .string()
      .describe('Amazon geo location (e.g., 10001 for US ZIP code)')
      .optional();
  • Input schema definition for the amazon_sellers tool including query (seller ID), jsRender, domain, deviceType, and geo parameters.
    inputSchema: {
      query: z.string().describe('Amazon seller ID (e.g., "A1R0Z7FJGTKESH")'),
      jsRender: zodJsRender,
      domain: zodDomain,
      deviceType: zodDeviceType,
      geo: zodGeo,
    },
    annotations: {
  • The registerAllTools method (line 113-117) iterates over all tools including AmazonSellersTool and calls their register() method to register them with the MCP server.
    registerAllTools() {
      for (const tool of ScraperAPIBaseServer.allTools) {
        tool.register({ server: this.server, sapiClient: this.sapiClient, auth: this.auth });
      }
    }
  • The allTools static array (line 66-97) instantiates all tools, including new AmazonSellersTool() on line 77, making it available for registration.
    static allTools: Tool[] = [
      new ScrapeAsMarkdownTool(),
      new ScreenshotTool(),
      new GoogleSearchTool(),
      new GoogleAdsTool(),
      new GoogleLensTool(),
      new GoogleAiModeTool(),
      new GoogleTravelHotelsTool(),
      new AmazonSearchTool(),
      new AmazonProductTool(),
      new AmazonPricingTool(),
      new AmazonSellersTool(),
      new AmazonBestsellersTool(),
      new WalmartSearchTool(),
      new WalmartProductTool(),
      new TargetSearchTool(),
      new TargetProductTool(),
      new TiktokPostTool(),
      new TiktokShopSearchTool(),
      new TiktokShopProductTool(),
      new TiktokShopUrlTool(),
      new YoutubeMetadataTool(),
      new YoutubeChannelTool(),
      new YoutubeSubtitlesTool(),
      new YoutubeSearchTool(),
      new RedditPostTool(),
      new RedditSubredditTool(),
      new RedditUserTool(),
      new BingSearchTool(),
      new ChatGPTTool(),
      new PerplexityTool(),
    ];
Behavior3/5

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

Annotations already provide readOnlyHint=true and openWorldHint=true, indicating safe reading. The description adds 'automatic parsing' but does not elaborate on behavior like rate limits or data freshness. It is adequate but not detailed.

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

Conciseness3/5

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

The description is a single sentence and concise, but it sacrifices specificity. It could include more detail while remaining brief.

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

Completeness2/5

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

Without an output schema, the description should explain return values or error handling. It only mentions 'automatic parsing' without clarifying output structure, making it incomplete for a 5-parameter tool.

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?

All parameters are fully described in the input schema (100% coverage), so the description adds no additional meaning. The baseline of 3 is appropriate given the schema handles parameter explanation.

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

Purpose4/5

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

The description clearly states it scrapes Amazon seller information with automatic parsing, specifying the verb and resource. However, it does not differentiate from sibling tools like amazon_product or amazon_bestsellers, which could also involve seller data.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like amazon_product or amazon_search. There are no explicit when-to-use or when-not-to-use conditions mentioned.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Decodo/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server