Skip to main content
Glama

Full ranking for a category

get_ranking
Read-onlyIdempotent

The ranked list for one category and month: estimated share of purchases, change in percentage points vs the previous month, rank last month, US price, and the sources behind it. Optional region.

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": {
      "category": "<category>"
    },
    "name": "get_ranking"
  }
}

Input Schema

NameRequiredDescriptionDefault
osNo
brandNoOnly this brand
limitNoMax products (default 10)
monthNoMonth as YYYY-MM. Defaults to the latest month.
regionNoOptional region: a code (US, UK, EU, AU), a market (na, eu, uk, au) or a name like "Australia". Omit for the global ranking.
categoryYesCategory in plain words, e.g. "mascara", "foundation", "lip oil", "setting spray", or an id from list_categories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world operation, so the safety profile is covered. The description's added value is disclosing the shape of the response payload (share of purchases, delta in percentage points, prior rank, US price, sources), which matters because there is no output schema. It says nothing about result caps, ordering guarantees, or what 'sources' represents.

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?

A single front-loaded sentence that leads with what the tool returns and keeps the field enumeration tight. Every clause contributes information, though the trailing 'Optional region' fragment feels tacked on rather than integrated. No padding or redundant restatement of the title.

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 compensates by describing the returned columns, which is exactly what an agent needs to interpret results. The main gaps are the default limit of 10 and the max of 50, which live only in the schema, plus ambiguity around 'sources.' For a read-only ranking query this is close to sufficient.

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 83%, so most parameters are already documented, including the region format and the month pattern. The description reinforces that category and month together define the result set and that region is optional, but adds no syntax or default details beyond the schema. Baseline 3 is appropriate when the schema carries most of the weight.

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 names a specific resource (the ranked list) with a clear scope (one category and month) and enumerates the returned fields: share of purchases, percentage-point change, last month's rank, US price, and sources. That is far more than a restatement of the title. It stops short of explicitly distinguishing itself from the sibling best_in_category, which an agent could plausibly confuse it with.

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

Usage Guidelines2/5

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

The only guidance offered is 'Optional region,' and it does not say when to use this tool instead of best_in_category, trending, or search_products. There is no statement of when-not-to-use or what alternative fits a different need. An agent must infer the selection criteria from the sibling names alone.

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.

Resources