Skip to main content
Glama
tiktok-shop-mcp

tiktok-shop-mcp

by Buer2333

get_account_video_gmv_tool

Aggregate TikTok Shop video GMV by account username, filter specific accounts with comma-separated usernames, and return per-account GMV, orders, items sold, and video count.

Instructions

Auto-paginate all shop videos and aggregate GMV by account username. Pass usernames as comma-separated string (e.g. 'dr.elise,dr.camila') to filter specific accounts. Returns per-account totals: gmv, orders, items_sold, video count.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_account_video_gmv_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
currencyNoUSD
usernamesNo
end_date_ltNo
seller_nameNo
account_typeNoALL
start_date_geNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose one genuinely useful behavior: it auto-paginates internally so the agent needn't loop. It also names the per-account output fields. However, it says nothing about permissions, rate limits, how date bounds affect aggregation scope, or what happens with sellers/accounts that have no videos.

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?

Three tight sentences: scope and aggregation first, filter syntax second, return shape third. Every sentence adds information and nothing is padded or repeated from the schema.

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?

An output schema exists, so the return-value summary is a bonus rather than a necessity. Still, for a six-parameter, zero-coverage tool with no annotations, the description leaves the date-range semantics and non-username filters undocumented, which an agent needs to scope a GMV aggregation correctly.

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?

Schema description coverage is 0%, so the description must compensate for all six parameters, but it only documents one: the comma-separated usernames format with an example, which is valuable since the schema supplies no format hint. The date range params (start_date_ge, end_date_lt), currency, seller_name, and account_type are entirely unexplained, leaving the agent guessing at accepted date formats and enum-like values such as account_type 'ALL'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('aggregate GMV by account username' over shop videos) that an agent can act on immediately. It is clearly more specific than generic siblings like get_shop_videos_performance_tool, but it never explicitly names or contrasts with those tools, so differentiation is inferred rather than stated.

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 only guidance is how to supply the usernames filter ('comma-separated string'), which is parameter usage, not when-to-use. There is no statement of when this tool should be chosen over get_shop_videos_performance_tool, get_creators_bestselling_tool, or any other sibling, and no preconditions or exclusions are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.