Skip to main content
Glama
pos-buzz

posbuzz-mcp

Official
by pos-buzz

delete_ec_sales

Delete synced EC sales data by channel or import batch. Specify source_channel and optional import date to remove either that day's sync or the entire channel's data.

Instructions

Deletes synced EC sales data for a channel. Provide source_channel (required) and optionally imported_on:

  • with imported_on → deletes only that import batch (the rows synced on that date).

  • without imported_on → deletes the entire channel.

Deletion is idempotent: deleted_count is 0 when nothing matched. Use read_ec_sync_status to discover the channels and import dates available to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
imported_onNoOptional import date (YYYY-MM-DD). Omit to delete the whole channel.
source_channelYesChannel to delete (normalized server-side).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesOutcome of an EC sales deletion (delete_ec_sales). Deletion is idempotent — deleted_count is 0 when nothing matched.
Behavior4/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. It discloses important behaviors: batch vs. whole-channel deletion, idempotency (deleted_count 0 on no match), and the availability of a discovery sibling. It does not mention irreversibility or permissions, but the core behavioral nuances are well covered.

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 concise and well-structured. The bullet list efficiently clarifies the conditional behavior, and the final sentences on idempotency and discovery add valuable context without redundancy. Every sentence earns its place.

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?

Given an output schema exists, the description covers the essential aspects: how to target specific batches vs. whole channels, idempotent behavior, and how to discover valid inputs. It could mention the destructive nature more explicitly, but overall it is complete enough for a destructive tool with clear parameters.

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%, with both parameters already described in detail. The description re-emphasizes the conditional behavior of imported_on and adds clarity via bullet points, but does not substantially extend beyond schema semantics. Baseline 3 is appropriate.

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 verb 'Deletes', the resource 'synced EC sales data', and the scope 'for a channel'. It distinguishes itself from siblings like import_ec_sales (opposite operation) and read_ec_sync_status (discovery), making its purpose unambiguous.

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

Usage Guidelines4/5

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

The description provides clear conditional usage (with or without imported_on) and explicitly directs users to read_ec_sync_status for discovering valid channels and dates. It lacks an explicit 'when not to use' exclusion, but the guidance is sufficient for selecting this tool correctly.

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/pos-buzz/posbuzz-mcp'

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