Skip to main content
Glama

Nexscope Ecommerce Data MCP

ET TikTok Influencer Detail

nexscope_data_et_influencer_detail
Read-only

Read profiles for up to 10 TikTok influencers by either numeric IDs or handles.

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": "nexscope_data_et_influencer_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdsNoNumeric influencer IDs; choose this or uniqueIds.
uniqueIdsNoTikTok handles without @; choose this or userIds.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered by structured data. The description adds the batch ceiling of 10, which is useful context, but says nothing about what happens on unknown handles, partial failures, or rate limiting.

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?

A single front-loaded sentence with no filler; the batch limit and the accepted key types appear before anything else. Nothing could be trimmed without losing information.

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 two-parameter read-only lookup with full schema coverage, the minimum an agent needs is present. However, with no output schema the description could say what a 'profile' returns or how sparse records are handled, and it omits any note about behavior when both key arrays are supplied.

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% and each parameter already states 'choose this or the other', including that handles omit '@'. The description's 'by either numeric IDs or handles' only restates that choice and adds no syntax, format or validation 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 specific verb and resource ('Read profiles for up to 10 TikTok influencers') plus the two lookup keys, which clearly separates it from the sibling detail tools for products, videos, sellers and categories. It stops short of naming any sibling explicitly, so the differentiation comes only from the resource noun.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied: use this when you already have influencer IDs or handles and want profile data. There is no statement of when not to use it, no pointer to an alternative (e.g. the trend or list tools) for discovery, and no mention that the two key types are mutually exclusive.

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