Skip to main content
Glama
Sign In
shopino-mcp

shopino-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Deals, flash sale and campaigns

sh_deals
Read-onlyIdempotent

Find today's flash sales, best sellers, themed deal rows, running campaigns, and shop discount codes, sorted by biggest discount, to see what's on sale now.

Instructions

List today's home-page deals (flash sale with end time, best sellers, themed rows), biggest discount first, plus running campaigns and shop discount codes.

Use for "what's on sale". Open a campaign: sh_campaign(slug).

Input Schema

NameRequiredDescriptionDefault
limitNoMax deals to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.0
    • changedInput schema / properties / limit / default
      Previous value: -30New value: +20
    • removedInput schema / properties / limit / title
      Removed value: -"Limit"
    • removedInput schema / title
      Removed value: -"sh_dealsArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "sh_dealsDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so safety is covered. The description adds genuine context beyond that: the ordering rule ('biggest discount first') and the composition of the result set, plus the follow-up tool for campaign detail. It does not mention pagination, refresh cadence, or locale/personalization effects, which keeps it at 4 rather than 5.

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?

Two short sentences with zero filler: the content/ordering statement is front-loaded and the routing hint is compact. Every clause carries information an agent needs.

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?

With no output schema, the description usefully enumerates what the response contains (flash sale with end time, best sellers, themed rows, campaigns, discount codes), which is the right compensation. Minor gaps remain about whether results are personalized or region-dependent given openWorldHint=true, but nothing blocks a correct call.

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 coverage is 100% with a single optional 'limit' parameter already documented as 'Max deals to return'. The description's ordering statement indirectly tells the agent what counts as the top-N cut, but adds no format or constraint detail beyond the schema, so the 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 ('List') and a precisely scoped resource: today's home-page deals, including flash sale with end time, best sellers, themed rows, running campaigns and shop discount codes. An agent can tell this apart from sh_search/sh_browse because the 'what's on sale' framing pins it to curated merchandising rather than query-driven lookup.

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

Usage Guidelines4/5

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

Gives an explicit trigger phrase ('Use for "what's on sale"') and a concrete next step, routing to sh_campaign(slug) to open a campaign. It lacks a when-not clause or a stated boundary against siblings like sh_search, so it is strong but not fully exhaustive.

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

Deploy Server

Other Tools