Skip to main content
Glama

Nexscope Ecommerce Data MCP

Nexscope aliexpress google organic search

nexscope_aliexpress_google_organic_search

Search Google organic results for AliExpress research. Results are search listings, not verified AliExpress products.

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": {
      "requestId": "<requestId>",
      "keyword": "<keyword>"
    },
    "name": "nexscope_aliexpress_google_organic_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
keywordYesThe normalized keyword must be at most 120 characters.
pageNumNo
requestIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior2/5

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

The one genuinely useful addition is the warning that results are unverified search listings, which sets expectations for result quality. However, annotations declare readOnlyHint=false and openWorldHint=true with no explanation of what is mutated or created (task creation?), and there is no disclosure of rate limits, async/polling behavior, or result freshness despite several siblings having task_result tools.

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?

Two tight sentences with the primary purpose front-loaded and a useful caveat second; nothing is wasted. Minor deduction because the caveat could be folded into a clearer scope statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must carry the weight of return-value and behavioral explanation, and it falls well short — no result shape, no pagination behavior, no mention of the non-readOnly annotation, and three undocumented parameters.

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 coverage is only 25% and the description explains none of the four parameters — not keyword normalization, not the limit/pageNum pagination caps, not requestId's role. The description does not compensate for the thin schema, leaving the agent to infer pagination semantics.

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 (search Google organic results) scoped to AliExpress research, and the second sentence distinguishes the output type from verified product data. An agent can tell it apart from nexscope_aliexpress_product_search by the 'listings, not verified products' caveat, though the distinction is implicit rather than explicit.

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?

'For AliExpress research' implies the use case but gives no explicit when-to-use versus the many sibling search tools, and no when-not-to-use. Alternatives such as the product search or other Google search variants are never named.

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