Skip to main content
Glama

Listing analytics

items_post_item_analytics
Read-onlyIdempotent

Retrieve extended statistical metrics for listings over a period, including views, contacts, and presenceSpending. Filter by category or employee, sort by any metric, and group by day, week, month, or item.

Instructions

Returns EXTENDED statistical metrics for the profile/listings over a period (post_item_analytics, stats v2): views, contacts, presenceSpending, etc. with flexible grouping, filters and sorting. Read-only analytics. Choose it over items_post_item_stats_shallow when you need filters by category/employee, sorting by a metric, or presence-spending metrics. limit ≤ 1000.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateFromYesStart of the period, inclusive (YYYY-MM-DD).
dateToYesEnd of the period, inclusive (YYYY-MM-DD).
metricsYesList of requested metrics (at least 1): views, contacts, presenceSpending, etc.
groupingYesHow to group the metrics: period (day|week|month), itemId (by listing) and/or by category. An empty object — overall totals.
limitYesMaximum number of rows in the response (0..1000) for pagination.
offsetYesOffset from the start of the selection for pagination (>= 0).
filterNoSelection filters: categoryIDs — an array of category IDs, employeeIDs — an array of employee IDs. Without the filter — the entire profile.
sortNoSorting of results: key — the metric name, order — asc (ascending) or desc (descending).
user_idNoID of the owner user. Defaults to Profile_id from .env.
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description reinforces 'Read-only analytics' and adds specific metrics and capabilities (grouping, filters, sorting), providing context beyond annotations without contradiction.

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?

Two sentences with no wasted words: first sentence states what it returns and examples, second gives usage guidance and a constraint. Information is front-loaded and every sentence is necessary.

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?

For a tool with 9 parameters, nested objects, and no output schema, the description provides sufficient context: metric types, grouping options, filtering, sorting, and pagination limit. It lacks response format details but covers key operational aspects.

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 coverage is 100% with each parameter having a description. The description adds high-level context ('flexible grouping, filters and sorting') but does not detail individual parameters, which is acceptable given the schema already does so.

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 it returns extended statistical metrics for profile/listings over a period, listing examples like views, contacts, and presenceSpending. It distinguishes itself from the sibling tool items_post_item_stats_shallow, 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 Guidelines5/5

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

Explicitly guides when to use this tool over the alternative: 'Choose it over items_post_item_stats_shallow when you need filters by category/employee, sorting by a metric, or presence-spending metrics.' Also includes constraint 'limit ≤ 1000'.

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/elchin92/avito-mcp'

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