Skip to main content
Glama

search_products

Search for products in the SAP Commerce Cloud catalog using a query string, with options to control pagination for result management.

Instructions

Search for products in the Hybris catalog using a query string

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesSearch query for products
pageSizeNoNumber of results per page (default: 20)
currentPageNoPage number to retrieve (0-indexed, default: 0)

Implementation Reference

  • The `searchProducts` method in the `HybrisClient` class performs the API request to retrieve product search results from the Hybris OCC API.
    async searchProducts(query: string, pageSize = 20, currentPage = 0): Promise<ProductSearchResult> {
      const params = new URLSearchParams({
        query,
        pageSize: pageSize.toString(),
        currentPage: currentPage.toString(),
        fields: 'products(code,name,description,price,stock,categories,images),pagination',
      });
    
      return this.request<ProductSearchResult>(
        `/occ/v2/${encodeURIComponent(this.config.baseSiteId!)}/products/search?${params}`
      );
    }
  • src/index.ts:104-125 (registration)
    The `search_products` tool is registered in the `tools` array definition.
    {
      name: 'search_products',
      description: 'Search for products in the Hybris catalog using a query string',
      inputSchema: {
        type: 'object',
        properties: {
          query: {
            type: 'string',
            description: 'Search query for products',
          },
          pageSize: {
            type: 'number',
            description: 'Number of results per page (default: 20)',
          },
          currentPage: {
            type: 'number',
            description: 'Page number to retrieve (0-indexed, default: 0)',
          },
        },
        required: ['query'],
      },
    },
  • The `CallToolRequestSchema` handler calls the `hybrisClient.searchProducts` method when the tool `search_products` is requested.
    case 'search_products':
      result = await hybrisClient.searchProducts(
        validateString(args, 'query', true),
        validateNumber(args, 'pageSize', { min: 1, max: 100 }),
        validateNumber(args, 'currentPage', { min: 0 })
      );
      break;
Behavior2/5

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It mentions 'using a query string' but doesn't disclose key traits like whether this is a read-only operation, how results are returned (e.g., pagination details beyond schema), performance expectations, or error handling, which are critical for a search tool.

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, efficient sentence with zero wasted words. It front-loads the core purpose ('Search for products') and includes essential context ('in the Hybris catalog using a query string'), making it highly concise and well-structured.

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 complexity of a search tool with 3 parameters, no annotations, and no output schema, the description is incomplete. It lacks details on return values (e.g., result format), behavioral constraints (e.g., rate limits), or error cases, leaving significant gaps for the agent to operate effectively.

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?

Schema description coverage is 100%, so the schema fully documents parameters like 'query', 'pageSize', and 'currentPage'. The description adds no extra meaning beyond implying a search context, meeting the baseline for high schema coverage without compensating with additional insights.

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 action ('Search for products') and resource ('in the Hybris catalog'), making the purpose evident. However, it doesn't differentiate from sibling tools like 'get_product' (which likely retrieves a specific product) or 'flexible_search' (which might offer more advanced querying), leaving room for ambiguity in tool selection.

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 prerequisites, such as needing a query string, or compare it to siblings like 'get_product' for single-product retrieval or 'flexible_search' for complex queries, leaving the agent to infer usage context.

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/mcieunic/hybris-mcp-main'

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