Skip to main content
Glama
pos-buzz

posbuzz-mcp

Official
by pos-buzz
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

import_ec_sales

Import e-commerce sales data from CSV or JSON, mapping columns to required fields and upserting rows by channel, product, and sale date.

Instructions

Imports EC sales data into the tenant. Choose one of two payload types via payload_type:

payload_type=csv (default)

Sync a source CSV (e.g. a sales export downloaded from Amazon, Rakuten, or your own EC).

  1. Download the sales CSV from the EC mall to a local file.

  2. Base64-encode the file's bytes and send it as csv_payload.

  3. Map each CSV column header to the five required normalized fields via mapping: product_id, product_name, sold_on, sales_amount, sales_quantity.

payload_type=json

Send the rows directly as records — an array of objects keyed by the canonical field names. No mapping or csv_payload is needed.

For both modes set source_channel (e.g. amazon, rakuten, owned) — it is normalized (lowercased, spaces → dashes).

Notes

  • Rows are upserted on the business key (source_channel × product_id × sold_on). Re-sending the same rows updates them in place — the sync is idempotent.

  • sold_on must be a complete date (year, month, and day). Accepted formats: YYYY-MM-DD, YYYY/MM/DD, YYYY.MM.DD.

  • sales_amount and sales_quantity must be zero or greater. Currency symbols/commas in amounts are stripped.

  • On any row or mapping error nothing is written and a 422 is returned with the per-row messages in error.details.errors.

  • After syncing, confirm with read_ec_sync_status. Individual sales rows are never readable back through the API.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mappingNoMaps each required normalized field to the matching CSV column header. Required (all five keys) when payload_type=csv.
recordsNoSales rows keyed by the canonical field names. Required when payload_type=json.
filenameNoOptional original filename, for display only (csv mode).
csv_payloadNoBase64-encoded CSV file contents (headers + rows). Required when payload_type=csv.
payload_typeNo`csv` (default): send base64 `csv_payload` + `mapping`. `json`: send `records`.csv
source_channelNoEC channel the rows belong to. Normalized before storage.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesOutcome of an EC sales CSV sync (import_ec_sales). Rows are upserted on the business key (source_channel × product_id × sold_on), so re-sending the same rows updates in place rather than duplicating.

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavior: idempotent upserts on the business key, accepted date formats, non-negative validation, stripping of currency symbols, atomic error behavior returning 422 with per-row details, source_channel normalization, and the fact that individual sales rows are never readable back. This is exemplary transparency.

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, numbered steps for the csv mode, and concise notes. It is appropriately sized for a complex tool with multiple payload types and every sentence contributes useful information.

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

Completeness5/5

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

Given the tool's complexity, the description covers both modes, error behavior, idempotency, date formats, validation, and post-sync confirmation. An output schema is present, so return value details are not required; the description is complete for selection and invocation.

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

Parameters4/5

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

The input schema already has 100% parameter coverage with descriptions. The tool description adds meaningful workflow semantics: how csv_payload and mapping relate, how records work for json mode, source_channel normalization, and filename being display-only. This adds value beyond the schema, though the schema already carried much of the load.

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 starts with a specific verb and resource: 'Imports EC sales data into the tenant.' It further distinguishes itself from siblings by detailing two payload modes and clarifying that it is the import tool, while siblings handle read, sync status, deletion, etc.

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 gives clear usage guidance: choose csv vs json, base64 encode the CSV, provide mapping, and confirms after syncing with read_ec_sync_status. It does not explicitly state when not to use the tool or mention delete_ec_sales as an alternative, so it stops short of a 5.

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