Skip to main content
Glama
kavingas

Catalog Services MCP Server

by kavingas

get_products

Retrieve product details from Adobe Commerce Catalog Service by providing environment ID, store view code, store code, website code, and product SKUs.

Instructions

Get product details from Catalog Service via gRPC.

This tool calls the GetProducts RPC method to retrieve product information
from the Adobe Commerce Catalog Service.

Args:
    environment_id: Adobe Commerce Cloud environment ID (e.g., 'abc123xyz')
    store_view_code: Store view code (e.g., 'default')
    store_code: Store code (e.g., 'main_website_store')
    website_code: Website code (e.g., 'base')
    skus: List of product SKUs to retrieve
    use_tls: Whether to use TLS connection (default: True)
    timeout: Request timeout in seconds (default: 15.0)
    
Returns:
    Dict containing product information with keys:
    - products: List of product dictionaries
    - count: Number of products retrieved
    - status: Success or error status
    
Example:
    >>> result = get_products(
    ...     environment_id='abc123xyz',
    ...     store_view_code='default',
    ...     store_code='main_website_store', 
    ...     website_code='base',
    ...     skus=['SKU123', 'SKU456']
    ... )
    >>> print(result['count'])
    2

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
skusYes
timeoutNo
use_tlsNo
store_codeYes
website_codeYes
environment_idYes
store_view_codeYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description carries full burden. It states it retrieves product information, implying no destructive actions, but lacks details on authentication, rate limits, error handling, or data freshness. Adequate but not exhaustive.

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

Conciseness4/5

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

Well-structured with a heading, Args/Returns/Example sections. Front-loaded with purpose. Slightly long but each part earns its place; could be condensed slightly but remains clear.

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?

Covers parameters, return structure, and an example. The output schema exists (though not shown) so return values need not be fully explained. Missing details like error codes or pagination, but sufficient for typical use.

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

Parameters5/5

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

Schema has 0% description coverage, but the description provides meaningful parameter descriptions for all 7 parameters (e.g., 'environment_id: Adobe Commerce Cloud environment ID') and specifies defaults for timeout and use_tls, adding value beyond the schema.

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?

The description clearly states it gets product details from Catalog Service via gRPC, citing the GetProducts RPC method. It distinguishes from siblings like get_category_permissions by focusing on products.

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 on when to use this tool versus the sibling tools. It does not mention alternatives or contexts where this tool is preferred, merely documenting the function.

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/kavingas/catalog-services-mcp'

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