Skip to main content
Glama

Nexscope Ecommerce Data MCP

ET TikTok Influencer Trend

nexscope_data_et_influencer_trend
Read-only

Read one page of an influencer daily trend within the last 180 days.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "userId": "<userId>",
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "nexscope_data_et_influencer_trend"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYesInfluencer numeric ID.
endDateYesEnd date, yyyy-MM-dd.
pageNumNoOne page per call.
pageSizeNoRecords per page, at most 10.
startDateYesStart date, yyyy-MM-dd.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this a safe, non-destructive read against an open world, so the safety profile is covered elsewhere. The description adds two genuinely useful behavioral facts: results are paged and limited to a 180-day lookback. It says nothing about what happens when the date range exceeds 180 days or whether empty/invalid IDs error out.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler or redundant restatement of the name. It is arguably too sparse for a five-parameter tool with no output schema, which keeps it from a 5.

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?

For a read-only trend tool with full schema coverage and annotations, the essentials for calling it are present. However, with no output schema, the description never indicates what a trend record contains (metric fields, daily granularity, ordering), leaving an agent unable to judge whether the response fits its need.

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%, so every parameter (userId, startDate, endDate, pageNum, pageSize) is already documented, making baseline 3 appropriate. The description adds only the date-window limit and the one-page-per-call notion, which lightly reinforces pageNum but does not add format or range detail beyond the schema.

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 concrete verb and resource ('Read one page of an influencer daily trend') plus a scoping constraint (last 180 days), so an agent knows exactly what is returned. It stops short of differentiating itself from near-siblings like nexscope_data_et_influencer_detail or nexscope_data_et_category_trend, which is why it is not a 5.

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?

There is no guidance on when to pick this over the influencer detail or category trend tools, and no statement of prerequisites such as needing a valid influencer ID first. The only implicit cue is the pagination phrasing 'one page', which hints at iterative calls but never says so.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources