Skip to main content
Glama

pospal_delete_categories

Batch delete product categories by supplying a list of category UIDs.

Instructions

【写】批量删除分类(category_uids 为 uid 字符串列表)。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
category_uidsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It indicates mutation via '【写】' (write) and 'delete', but lacks details on destructiveness, irreversibility, permissions, or return value. For a delete operation, more context is needed.

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?

The description is a single sentence with a clear action indicator and parameter hint. It is concise but could be more structured (e.g., separating behavior from parameter explanation). The Chinese text is appropriate for the tool's audience.

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

Completeness3/5

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

The tool is simple with one parameter, and an output schema exists (not shown here). However, the description does not mention the outcome of the batch delete (e.g., success confirmation, count of deleted categories). Minimal but adequate for a straightforward delete action.

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

Parameters2/5

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

The only parameter, category_uids, is described as 'uid 字符串列表' (list of uid strings), which merely restates the schema type. With 0% schema description coverage, the description does not add meaningful context like format or constraints (e.g., minimum length, uniqueness).

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 explicitly states the verb 'delete' and the resource 'categories', with 'batch' indicating multiple items. It distinguishes from siblings like pospal_delete_customer and pospal_delete_product by specifying the target resource.

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 vs alternatives such as pospal_list_categories for viewing or pospal_update_category for modification. No conditions or prerequisites are mentioned.

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/ironfrancis/FastPospal'

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