Skip to main content
Glama

List a retailer's authorized brands

get_retailer_brands
Read-onlyIdempotent

List all brands a retailer (shop) is currently authorized to sell, according to authorized.by. Read-only. Use this to answer 'which brands has shop X been authorized for?'. Sorted by brand name. Each entry includes official_shop, partnership_date, and certificate_url / certificate_url_de: links to the public authorized.by certificate page (English / German) proving this specific brand-retailer authorization. Share the certificate link when a user needs verifiable proof. Only active partnerships are returned: confirmed by both the brand and the retailer, with both profiles public and both companies approved by authorized.by. Revoked or pending partnerships are never listed. Responses are cached and refreshed when the underlying profile or partnership changes, so a revocation may take a short time to disappear. partnership_date is the date the authorization STARTED, not the date it was last verified; a partnership listed here is currently active as of the response time. Data scope: results only cover relationships registered and confirmed on authorized.by. An empty result or a not-found error does NOT prove that no authorization exists outside authorized.by. Distinguish outcomes: an empty list means no matching record on authorized.by; an error result whose text starts with 'Brand not found' or 'Retailer not found' means the given id/alias is unknown; an error result whose text starts with 'Tool execution failed' is a technical error and says nothing about the 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": {
      "id_or_alias": "<id_or_alias>"
    },
    "name": "get_retailer_brands"
  }
}

Input Schema

NameRequiredDescriptionDefault
id_or_aliasYesRetailer numeric ID, slug or alias.

Output Schema

NameRequiredDescriptionDefault
totalYesNumber of entries in the list.
brandsYes
retailer_idYesNumeric ID of the retailer the list belongs to.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedOutput schema / properties / brands / items / properties / certificate_url / description
      Previous value: -"Public authorized.by certificate page (English) that proves the authorization; null when there is no active authorization."New value: +"Public authorized.by certificate page (English) that proves the authorization: of this brand and retailer where the entry is about both, otherwise the retailer's page listing all brands that authorize it. Null when there is no active authorization."
    • changedOutput schema / properties / brands / items / properties / official_shop / description
      Previous value: -"Whether this shop is the brand's own official shop."New value: +"true when this shop is the brand's own official online shop, false when it is an independent authorized retailer. In verify_retailer_authorization it is null unless the status is AUTHORIZED."
    • changedOutput schema / properties / brands / items / properties / partnership_date / description
      Previous value: -"Date (YYYY-MM-DD) the authorization STARTED. Not a last-verified date: every listed partnership is active as of the response."New value: +"Date (YYYY-MM-DD) this brand's authorization of this retailer STARTED on authorized.by. Not the date either company joined authorized.by and not a last-verified date: every listed partnership is active as of the response."
  2. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / id_or_alias / description
      Previous value: -"Retailer numeric ID or alias."New value: +"Retailer numeric ID, slug or alias."
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "description": "All brands that currently authorize the retailer, with per-brand certificate links.",
      +  "properties": {
      +    "brands": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "certificate_url": {
      +            "description": "Public authorized.by certificate page (English) that proves the authorization; null when there is no active authorization.",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "certificate_url_de": {
      +            "description": "Same certificate page in German; null when there is no active authorization.",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "id": {
      +            "description": "Numeric authorized.by ID. Accepted by the id_or_alias argument of the detail tools.",
      +            "type": "integer"
      +          },
      +          "logo": {
      +            "description": "Logo image URL, or null.",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "name": {
      +            "description": "Display name.",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "official_shop": {
      +            "description": "Whether this shop is the brand's own official shop.",
      +            "type": "boolean"
      +          },
      +          "partnership_date": {
      +            "description": "Date (YYYY-MM-DD) the authorization STARTED. Not a last-verified date: every listed partnership is active as of the response.",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "slug": {
      +            "description": "URL-safe identifier. Accepted by the id_or_alias argument of the detail tools.",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "website_url": {
      +            "description": "Brand website URL, or null.",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "name",
      +          "slug",
      +          "website_url",
      +          "logo",
      +          "official_shop",
      +          "certificate_url",
      +          "certificate_url_de",
      +          "partnership_date"
      +        ],
      +        "type": "object"
      +      },
      +      "type": [
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "retailer_id": {
      +      "description": "Numeric ID of the retailer the list belongs to.",
      +      "type": "integer"
      +    },
      +    "total": {
      +      "description": "Number of entries in the list.",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "retailer_id",
      +    "total",
      +    "brands"
      +  ],
      +  "type": "object"
      +}
  3. Added

TDQS

A4.4/5.0
Behavior5/5

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

It adds substantial behavior beyond the annotations: sorted ordering, included fields, certificate-link semantics, active-only filtering, cache refresh delay, and the fact that partnership_date is the start date rather than a verification date. It also distinguishes empty-list, not-found, and technical-error outcomes and warns that absence on authorized.by does not prove no authorization exists elsewhere.

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?

The description is front-loaded with purpose and structured into readable guidance, and the length is justified by the caching, scope, and error-state caveats. Some sentences are redundant, such as repeating that only active partnerships are returned and that revoked or pending partnerships are never listed.

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

Completeness5/5

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

For a single-parameter read-only lookup with an output schema, the description covers purpose, active-only behavior, caching effects, field meanings, certificate usage, data scope, and error distinctions. Nothing material appears missing for correct tool selection and invocation.

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% for the single parameter, so the schema already documents id_or_alias as a retailer numeric ID, slug, or alias. The description reinforces that the identifier refers to a retailer but does not add syntax or format guidance beyond the schema.

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?

The description states a specific verb and resource: list all brands a retailer is currently authorized to sell. It also makes the direction of lookup clear (retailer to brands) and identifies the authoritative source, authorized.by, so it is distinguishable from reverse-lookup siblings.

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?

It gives explicit usage context with the example question 'which brands has shop X been authorized for?' and says to share the certificate link when proof is needed. It does not explicitly name when to use a sibling tool instead, but the retail-directed use case is clear.

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