Papyras Coupons

Coupons for a store

get_store_offers

Read-onlyIdempotent

All live coupon codes and deals for one store, best first. The store can be a name ("Nike"), a domain ("nike.com"), a URL, or a Papyras store slug. Each offer shows whether the network marked it verified and what shoppers reported.

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": {
      "store": "<store>"
    },
    "name": "get_store_offers"
  }
}

Input Schema

Name	Required	Description
`type`	No	Only codes or only deals (optional).
`limit`	No	How many offers to return (default 10, max 50).
`store`	Yes	Store name, domain, URL or slug.
`country`	No	Optional ISO country code (US, UK, DE, …) to prefer stores that serve that country. Worldwide stores are always included.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive profile, so the description's job is to add more. It does: 'live' discloses that expired coupons are filtered out, 'best first' discloses result ordering, and the closing sentence discloses that each offer carries verification status and shopper-reported outcomes — meaningful return-value context with no output schema present.

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 sentences, zero filler, and the most decision-relevant facts — scope, freshness, ordering — are front-loaded. The second sentence earns its place by describing return contents that no output schema provides.

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 four-parameter read tool with full schema coverage, this covers the essentials, including what a returned offer contains, which compensates for the absent output schema. It stops short of stating whether limit caps at 50, whether results are paginated, or how country preference affects ranking, but those are modest gaps given the schema's enum, min/max, and country documentation.

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 the schema already documents all four parameters including the accepted store identifier forms. The description's enumeration of name/domain/URL/slug largely restates the schema, and it says nothing about limit, type, or country beyond what is written there. Baseline 3 is appropriate.

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: 'All live coupon codes and deals for one store, best first' — an agent immediately knows it retrieves store-scoped offers with a defined ordering. It scopes to a single store, which implicitly separates it from category- or URL-level siblings, but never names them.

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?

Usage is only implied: an agent can infer this is the tool when it already has a store identifier in hand. Nothing addresses when to prefer best_offer_for_url (which also takes a URL) or top_offers_in_category, and no exclusions are given despite the description acknowledging URL input.

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

All Papyras Coupons tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?