Skip to main content
Glama
sepehr071

shopino-mcp

by sepehr071
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Campaign page

sh_campaign
Read-onlyIdempotent

Open a campaign or landing page by slug to retrieve product rows with prices and tabs for browsing curated deals.

Instructions

Open a campaign or landing page: its product rows (with prices) and tabs.

A tab's source: listing -> sh_browse(listing=...), shop_id / category_id -> sh_browse(same), flash_sale -> sh_deals.

Input Schema

NameRequiredDescriptionDefault
slugYesSlug from sh_deals campaigns, e.g. 'sale07', or 'clothing', 'bag', 'shoes', 'sports'.
per_rowNoProducts per row.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.3.0
    • changedInput schema / properties / per_row / description
      Previous value: -"Products to show per product row."New value: +"Products per row."
    • removedInput schema / properties / per_row / title
      Removed value: -"Per Row"
    • changedInput schema / properties / slug / description
      Previous value: -"Campaign / landing slug from sh_deals campaigns, e.g. 'sale07', or a top category's: 'clothing', 'bag', 'shoes', 'sports'."New value: +"Slug from sh_deals campaigns, e.g. 'sale07', or 'clothing', 'bag', 'shoes', 'sports'."
    • removedInput schema / properties / slug / title
      Removed value: -"Slug"
    • removedInput schema / title
      Removed value: -"sh_campaignArguments"
    • changedOutput schema / (root)
      Previous value: -{
-  "additionalProperties": true,
-  "title": "sh_campaignDictOutput",
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A3.9/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 open-world, so safety is covered. The description adds genuinely non-structured behavior: the page contains product rows with prices plus tabs, and tabs are not resolved inline but must be fetched via sh_browse or sh_deals. Pagination and the exact row/tab response shape remain undisclosed.

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 short sentences, front-loaded with the primary action and output, then the routing table for tab sources. No filler, though the backtick/arrow notation is terse enough to require a second read.

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?

For a two-parameter read tool with full schema coverage and no output schema, the description supplies the essentials: what the page yields, how tabs resolve, and which sibling tools continue the flow. It omits pagination and whether per_row changes the returned structure, which are minor gaps.

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 both `slug` and `per_row` are already documented in the schema, including the slug pattern, defaults and bounds. The description's mention of 'campaign or landing page' only loosely corroborates the slug semantics and adds no format or constraint detail, so the baseline of 3 applies.

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 ('open') and resource ('campaign or landing page') and enumerates the returned content (product rows with prices, tabs). It also distinguishes itself implicitly by routing tab sources to sh_browse and sh_deals, though the boundary versus sh_shop is not drawn explicitly.

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 conditional routing: a tab whose source is `listing`, `shop_id` or `category_id` goes to sh_browse, and `flash_sale` goes to sh_deals. That is clear follow-up guidance, but there is no explicit statement of when to call sh_campaign instead of sh_shop or sh_search.

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