MaxGaming MCP Server

Overview Schema Source Related Servers Discussions Admin

browse_page

Browse MaxGaming category, brand, or campaign pages by URL to return visible products and embedded product data for discovery and research.

Instructions

Browse a MaxGaming category, brand or campaign page. Returns visible products with embedded data.

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": {
      "url": "<url>"
    },
    "name": "browse_page"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Shop category, brand or campaign URL from MaxGaming.
`page`	No	Listing page, starting at 1; use next_page to continue.
`fresh`	No	Bypass the process cache and request current shop data.
`country`	No	Storefront country code. Defaults to us (International).	us
`language`	No	Shop language; defaults to the country's language. MaxGaming uses one language per storefront.

Output Schema

Name	Required	Default
`note`	No
`page`	Yes
`cache`	No
`count`	Yes
`query`	Yes
`paging`	Yes
`source`	Yes
`country`	No	us
`coverage`	Yes
`language`	No	en
`products`	Yes
`retailer`	Yes
`next_page`	Yes
`observed_at`	No
`local_filters`	No
`related_pages`	No
`redirected_url`	No
`total_products`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 13, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description must carry the load. 'Returns visible products with embedded data' hints at the payload shape, but it says nothing about whether the page is fetched live (the schema's `fresh` flag implies a cache), how failures or empty categories behave, or any throttling. Modest value, significant gaps.

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 action and scope, with no filler. The second sentence is marginally redundant given an output schema exists, but it is not bloat.

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

Completeness3/5

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

For a 5-parameter tool with an output schema and full parameter coverage, the description is acceptable but thin: it never explains that the URL must be an existing MaxGaming listing URL (left to the schema) or that paging is capped, which matters for multi-page crawling decisions.

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 `url`, `page`, `fresh`, `country` and `language` are already fully documented in the schema, including the page-30 cap and the 'use next_page to continue' note. The description adds no meaning beyond that, so the baseline 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?

The description gives a specific verb and resource: 'Browse a MaxGaming category, brand or campaign page.' That is clearly different from fetching one product (get_product) or searching (search_products), but it never names those siblings, so the separation is inferred rather than stated.

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?

The phrase 'category, brand or campaign page' implies the tool is for walking listing pages rather than free-text search, but the description never says when to prefer it over search_products or get_product, nor does it state any exclusions or prerequisites.

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

Deploy Server