Skip to main content
Glama
kavingas

Catalog Services MCP Server

by kavingas

get_category_permissions

Retrieve category permissions to control which customer groups can view categories on websites. Get permissions for specific categories or all categories.

Instructions

Get category permissions from Catalog Service via gRPC.

This tool calls the GetCategoryPermissions RPC method to retrieve category permission
information from the Adobe Commerce Catalog Service. Category permissions control
which customer groups can view specific categories on different websites.

Args:
    environment_id: Adobe Commerce Cloud environment ID (e.g., '3f73a49a-3137-472c-bb0d-39d0e7925d86')
    category_ids: Optional list of category IDs to retrieve permissions for. 
                 If not provided, returns permissions for all categories.
    use_tls: Whether to use TLS connection (default: True)
    timeout: Request timeout in seconds (default: 15.0)
    
Returns:
    Dict containing category permission information with keys:
    - permissions: List of permission dictionaries, each containing:
        - environment_id: Environment ID
        - category_id: Category ID
        - displayable_permission_by_website_code: Map of website codes to customer group permissions
        - created: Creation timestamp
        - updated: Last update timestamp
        - deleted: Whether the permission is deleted
    - count: Number of permissions retrieved
    - status: Success or error status
    
Example:
    >>> result = get_category_permissions(
    ...     environment_id='3f73a49a-3137-472c-bb0d-39d0e7925d86',
    ...     category_ids=['1', '2', '4']
    ... )
    >>> print(result['count'])
    3
    >>> for perm in result['permissions']:
    ...     print(f"Category {perm['category_id']}: {perm['displayable_permission_by_website_code']}")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
timeoutNo
use_tlsNo
category_idsNo
environment_idYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations exist, but the description fully discloses the operation (read via gRPC), the parameters, and the return format. It implies a read-only action without explicit statement, but the 'Get' verb and the example output suggest no side effects. One could argue a 5, but the lack of explicit statement on mutability or error behavior keeps it at 4.

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 well-structured with clear sections (Args, Returns, Example) and is appropriately sized. Every sentence adds value, with no fluff. The most important information (what, how, params) is front-loaded.

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?

The description includes parameter details, return format, and an example, making it complete for a retrieval tool. However, it does not mention error handling or edge cases (e.g., what happens if environment_id is invalid), and with no annotations, a bit more context on expected status codes could be beneficial.

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?

The input schema has 0% description coverage, but the tool description provides thorough explanations for all four parameters, including defaults, optionality, and examples (e.g., environment_id format, category_ids as optional list, use_tls default, timeout default). This adds significant semantic 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 the action ('Get category permissions'), the service ('Catalog Service via gRPC'), and the resource ('category permission information'), distinguishing it from siblings which deal with store views, environments, products, etc.

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

Usage Guidelines3/5

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

The description explains what the tool does but does not provide explicit guidance on when to use it versus alternatives or when not to use it. The purpose is clear enough to infer usage, but no comparative context is given.

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