Skip to main content
Glama
listingbureau

Listing Bureau - Amazon Organic Ranking

lb_projects_create

Create a new Amazon organic ranking project by specifying ASIN, keyword, and region. Reactivates archived projects with matching parameters.

Instructions

Create a new Listing Bureau Amazon project. If a project with the same ASIN+keyword+region was previously archived, it will be reactivated instead (returns 201). ASIN must be a valid Amazon ASIN. Keyword must be 3-200 characters.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
regionYesAmazon region code (GB accepted as alias for UK)
asinYesAmazon ASIN (e.g. 'B01MTJK06C')
keywordYesTarget keyword (3-200 characters)
expected_retail_priceNoExpected retail price of the product in USD. Required for SFB cost estimation and holds.

Implementation Reference

  • The async handler function for lb_projects_create. Builds request body with marketplace, region, asin, keyword, and optional expected_retail_price, then sends POST to /api/v1/projects and formats the response.
      async (params) => {
        try {
          const body: Record<string, unknown> = {
            marketplace: "amazon",
            region: normalizeRegion(params.region),
            asin: params.asin,
            keyword: params.keyword,
          };
          if (params.expected_retail_price !== undefined) {
            body.expected_retail_price = params.expected_retail_price;
          }
          const res = await client.request<Project>("POST", "/api/v1/projects", body, undefined, "lb_projects_create");
          return formatResult(res.data);
        } catch (e) {
          return formatErrorResult(e);
        }
      },
    );
  • Input schema for lb_projects_create: region (enum from ACCEPTED_REGIONS), asin (string), keyword (string 3-200 chars), expected_retail_price (optional number).
      region: z
        .enum(ACCEPTED_REGIONS)
        .describe("Amazon region code (GB accepted as alias for UK)"),
      asin: z
        .string()
        .describe("Amazon ASIN (e.g. 'B01MTJK06C')"),
      keyword: z
        .string()
        .min(3)
        .max(200)
        .describe("Target keyword (3-200 characters)"),
      expected_retail_price: z
        .number()
        .min(0)
        .optional()
        .describe("Expected retail price of the product in USD. Required for SFB cost estimation and holds."),
    },
  • src/index.ts:8-8 (registration)
    Import of registerProjectsTools from projects.tools.ts.
    import { registerProjectsTools } from "./tools/projects.tools.js";
  • src/index.ts:58-58 (registration)
    Registration call: registerProjectsTools(server, client) in index.ts which sets up all project tools including lb_projects_create.
    registerProjectsTools(server, client);
  • The Project type interface used as the response type for lb_projects_create (POST returns a Project).
    export interface Project {
      ui_id: string;
      cid: string;
      marketplace: string;
      region: string;
      asin: string | null;
      itemid: string | null;
      keyword: string;
      active: boolean;
      archived: boolean;
      dt_utc: string;
      product_id: string;
      services: {
        atc: number;
        sfb: number;
        pgv: number;
      };
      scheduling: ScheduleEntry[];
      data: {
        serps: Record<string, unknown>;
      };
      unavailable: boolean;
    }
Behavior4/5

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

Discloses the reactive behavior beyond annotations (idempotentHint: false). Adds context that expected_retail_price is needed for cost estimation and holds. Could mention permissions or rate limits, but the behavior is well-described.

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?

Three sentences covering purpose, reactivation behavior, and parameter constraints. No redundant information; each sentence adds essential detail. Front-loaded with main action.

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

Completeness4/5

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

For a create tool with no output schema and 4 parameters, the description covers behavior, constraints, and optional parameter purpose. Could mention error cases or ID generation, but the information is sufficient for correct invocation.

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 covers all parameters (100% coverage). Description adds value by explaining the purpose of expected_retail_price ('Required for SFB cost estimation and holds') and reinforces constraints on ASIN and keyword. This goes beyond the schema's basic descriptions.

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?

Clearly states 'Create a new Listing Bureau Amazon project' with a specific verb and resource. Distinguishes from sibling tools like lb_projects_archive or lb_projects_get by focusing on creation and reactivation behavior.

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

Usage Guidelines4/5

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

Provides context that reactivation occurs for archived projects with the same triple, and specifies constraints on ASIN and keyword. Does not explicitly state when not to use, but the purpose is clear and no direct alternatives exist.

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

Install Server

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/listingbureau/listingbureau-mcp'

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