Skip to main content
Glama

GoAI Moat Tiktok Shop

Server Details

Search TikTok Shop products by keyword.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
jayniebingyu-cyber/goaimoat-mcp
GitHub Stars
0

TDQS

A3.5/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion. The tool's purpose is clearly scoped to searching TikTok Shop products by keyword.

Naming Consistency5/5

The single tool name 'search_tiktok_products' follows a clean snake_case verb_noun convention, which is predictable and readable. There are no other tools to introduce inconsistency.

Tool Count2/5

A single tool for a TikTok Shop server feels far too thin for the apparent scope, which would typically require additional operations like product details, cart, or order management.

Completeness1/5

The server only supports keyword search and lacks any follow-up operations such as fetching product details, handling listings, or managing orders. The surface is severely incomplete and leaves agents with a dead end.

Available Tools

1 tool
search_tiktok_productsSearch Tiktok ProductsAInspect

Search TikTok Shop products by keyword.

ParametersJSON Schema
NameRequiredDescriptionDefault
keywordYesProduct keyword.

Output Schema

ParametersJSON Schema
NameRequiredDescription

No output parameters

TDQS

A3.6/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden, but it does not mention pagination, result limits, sorting, or whether the search is read-only. For a search tool, this is a significant omission. The description only states the action and parameter.

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?

The description is a single, focused sentence with no filler. It front-loads the action and parameter. Every word contributes.

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?

The tool is simple with a single fully-documented parameter and an output schema available. The description is sufficient for invoking the tool. Minor gap: no behavioral details like result counts, but the output schema can cover return format.

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?

The schema already documents the keyword parameter with 100% coverage ('Product keyword.'). The description's 'by keyword' merely restates the schema. No additional parameter semantics are provided, so baseline 3 applies.

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?

States a specific verb (Search), resource (TikTok Shop products), and method (by keyword). The title reinforces this. No ambiguity or tautology.

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?

The description implies the tool is for finding products by keyword, but there is no explicit guidance on when to prefer it over alternatives (none exist) or any exclusions. The context is minimal but understandable.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool update
    • First observedsearch_tiktok_products

Related MCP Connectors

Related MCP Servers

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.