Skip to main content
Glama

woolworths_get_product_details

Retrieve detailed product information from Woolworths Australia using the product stockcode to access pricing, specifications, and availability data.

Instructions

Get detailed information about a specific product by its stockcode

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
stockcodeYesThe product stockcode/ID

Implementation Reference

  • The handler function for woolworths_get_product_details. It takes a stockcode, constructs the Woolworths product detail API URL, fetches the data using makeWoolworthsRequest (which includes session cookies), and returns the product details or an error.
    async function handleGetProductDetails(args: any): Promise<any> {
      const stockcode = args.stockcode;
    
      const url = `https://www.woolworths.com.au/apis/ui/product/detail/${stockcode}`;
    
      try {
        const data = await makeWoolworthsRequest(url);
        return {
          success: true,
          product: data,
        };
      } catch (error: any) {
        return {
          success: false,
          error: error.message,
        };
      }
    }
  • The schema definition for the woolworths_get_product_details tool in the TOOLS array, specifying the input schema requiring a 'stockcode' string.
    {
      name: "woolworths_get_product_details",
      description:
        "Get detailed information about a specific product by its stockcode",
      inputSchema: {
        type: "object",
        properties: {
          stockcode: {
            type: "string",
            description: "The product stockcode/ID",
          },
        },
        required: ["stockcode"],
      },
    },
  • src/index.ts:643-645 (registration)
    The switch case in the CallToolRequestSchema handler that registers and dispatches to the woolworths_get_product_details handler function.
    case "woolworths_get_product_details":
      result = await handleGetProductDetails(args || {});
      break;
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it 'Get[s] detailed information', implying a read-only operation, but doesn't clarify aspects like whether it requires authentication, rate limits, error handling, or what format the information is returned in. For a tool with no annotations, this is a significant gap in transparency.

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?

The description is a single, clear sentence that directly states the tool's purpose without any unnecessary words. It is front-loaded with the core action and resource, making it highly efficient and easy to parse.

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?

Given the tool's complexity (a read operation with one parameter) and the absence of annotations and output schema, the description is incomplete. It doesn't explain what 'detailed information' entails, how results are structured, or any behavioral traits like error cases. For a tool with no structured output, more descriptive context is needed to be fully helpful.

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?

The input schema has 100% description coverage, with the parameter 'stockcode' documented as 'The product stockcode/ID'. The description adds no additional semantic context beyond this, such as examples or format details. According to the rules, with high schema coverage (>80%), the baseline score is 3, which is appropriate here.

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 the verb 'Get' and the resource 'detailed information about a specific product', making the purpose explicit. It distinguishes from siblings like 'woolworths_search_products' by focusing on a single product via stockcode rather than searching. However, it doesn't specify what 'detailed information' includes, which slightly limits differentiation.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention when to use it over 'woolworths_search_products' or other siblings, nor does it specify prerequisites like requiring a stockcode from another operation. This leaves usage context unclear.

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/elijah-g/Woolworths-mcp'

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