Skip to main content
Glama

MyProduct: Search Store Products

search_store_products
Read-onlyIdempotent

[Store Products] [What it does] Searches products directly on a seller's store platform (e.g. Shopify), not DSers My Products; used to inspect store products or as an import source. [When to use] Use to find what a store sells or to locate store products for importing into DSers. [When not to use] For products already managed in DSers, use list_managed_store_products; to import selected products, use import_store_products_to_dsers. [How to use] Copy dsers_store_id from list_stores; pages are 1-based; pass the previous next_since_id unchanged as since_id for the next page. Each item's already_imported state is included; an empty result is valid. [Side effects] Read-only; no store or DSers data changes. [Confirmation] No confirmation required. [Follow-up] If importing is the goal and the user selects products not already in DSers, continue with import_store_products_to_dsers; otherwise report the result and stop.

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": {
      "dsers_store_id": "<dsers_store_id>"
    },
    "name": "search_store_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo1-based page number; defaults to 1.
keywordNoProduct title keyword to search on the seller store. Optional.
since_idNoOpaque next_since_id returned by the previous call. Pass it unchanged.
page_sizeNoMaximum products to return; defaults to 20 and is capped by server configuration.
dsers_store_idYesCopy from list_stores response dsers_store_id field. Required.

Output Schema

NameRequiredDescriptionDefault
itemsYesSeller-platform product summaries
paginationYesCursor and page information
dsers_store_idYesQueried DSers store ID as a decimal string
toolcall_response_atYesUTC timestamp when the Tool response was returned, formatted as RFC3339.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world, so the safety profile is covered; the description nevertheless adds cursor mechanics (pass next_since_id unchanged as since_id), that empty results are valid, and that each item carries an already_imported flag. The 'Read-only; no data changes' and 'no confirmation required' lines partly restate the annotations, which keeps this from a 5.

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?

Bracketed section headers make it scannable and front-loaded with purpose before mechanics. It is on the long side for a five-parameter read tool and repeats the safety profile already in annotations, but no sentence is pure filler.

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

Completeness5/5

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

For a paginated read tool with an output schema available, the description covers what an agent needs: how to obtain the required store id, how pagination works across calls, what the response items contain, and what to do next. Return-value detail is correctly left to the output schema.

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 all five parameters are already documented in the schema, including 1-based paging, the opaque since_id passthrough, and where to copy dsers_store_id. The [How to use] block largely restates those same facts; the only marginal addition is pointing at list_stores as the origin of dsers_store_id, which the schema also says.

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 and resource (searches products on a seller's store platform) and explicitly scopes it against DSers My Products. The boundary against sibling tools like list_managed_store_products is drawn in the description itself, so an agent can choose without opening a schema.

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

Usage Guidelines5/5

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

Contains explicit [When to use] and [When not to use] sections, naming concrete alternatives (list_managed_store_products for already-managed products, import_store_products_to_dsers for importing). It also gives a follow-up routing rule for the import case, leaving nothing to inference.

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.