---
name: dattoria-analytics
description: Use Dattoria MCP to search and explain read-only Kaspi and Teez marketplace analytics, combine bounded reports, and export results. Use when a user asks about Dattoria products, categories, niches, brands, sellers, favorites, or marketplace metrics.
---

# Dattoria analytics

Use the connected Dattoria MCP tools to answer from the user's authorized analytics. Reply in the user's language and identify the marketplace, filters, and period behind each conclusion.

## Safe and accurate use

- If Dattoria MCP tools are not connected, say so. This skill does not itself authenticate or grant access.
- Never ask for an access key in chat. The user enters it only in the client's MCP settings. Never repeat, store, or include credentials in exports or prompts.
- Use only the registered read-only actions. Do not use a browser, website URL, arbitrary API, SQL, or another identity as a fallback. Do not change favorites, settings, or account data.
- Search the compact catalog with `search_actions`, then inspect each action with `describe_action`. Use only the documented fields and bounds.
- Read the live `rateLimits` object returned by discovery before making analytics calls. It includes the policy version, update time, request rates, and concurrency limits; the current values from the server are authoritative. Discovery calls do not consume analytics-call limits.
- Each underlying analytics action call counts toward the limits. Every workflow step and each separate original/translated search request counts individually. If the server rejects a call for rate or load, stop and wait; never retry through another key, identity, endpoint, or route.
- Specify the marketplace (`kaspi` or `teez`) for analytics. Send `dateFrom` and `dateTo` together in `YYYY-MM-DD`; ranges are limited to 180 days and cannot end in the future.
- Use `execute_action` for one report. Use `execute_workflow` for up to five related reports; the server validates all steps first and executes them sequentially. Shared marketplace/date defaults apply only where an action supports them; step arguments take precedence.
- Results from `search` and `searchAlias` remain separate. Compare them as distinct searches; do not add counts or claim they were merged or deduplicated.
- Check every result's `meta.completeness` and `meta.warnings`. Continue pagination only when useful and indicated; each call returns a bounded page. Never describe an unknown or partial result as complete.
- For a file, request `outputFormat: "json"` or `"csv"` on `execute_workflow`. The returned download link is temporary and expires after 15 minutes. Multi-step CSV is a ZIP with one file per successful step.
- If access, tariff, rate, or size limits block a request, explain the limit and stop. Do not try to bypass it by changing account, route, filters, or page size repeatedly.

## More detailed recipes

Read the `dattoria://workflows.md` resource only when a combined query, pagination, multilingual search, export, or result-quality question needs a worked example. It is a separate resource so the initial skill stays compact.

## Setup

The skill gives the agent instructions; the Dattoria MCP connection provides data access. Use only `https://mcp.dattoria.com/mcp` for the MCP endpoint and `https://mcp.dattoria.com/skill.md` or `/skill.zip` for this skill. Follow the selected client's current official setup instructions. Preserve existing client settings and other MCP servers. Never place a real key in this skill, a shared file, or a message; the user must enter it in the client's secure MCP credential field.