Skip to main content
Glama

Search brands

get_brands
Read-onlyIdempotent

Search brands (manufacturers) registered on authorized.by, or list them all. Read-only. 'search' matches the brand name, alias or website domain (partial match). Returns for each brand: id, name, slug, logo and the number of retailers it has authorized. Omit 'search' to retrieve the full index; use 'page' and 'size' to paginate. 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

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_brands"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoZero-based page number (default 0).
sizeNoPage size (default and maximum 500).
searchNoFilter by brand name, alias or website domain/URL, e.g. 'deuter' or 'deuter.com'. Optional.

Output Schema

NameRequiredDescriptionDefault
metaYesNetwork-wide totals.
brandsYes
paginationYesPagination of this response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / size / description
      Previous value: -"Page size (default 500)."New value: +"Page size (default and maximum 500)."
    • changedOutput schema / properties / brands / items / properties / retailer_count / description
      Previous value: -"Number of retailers currently authorized by this brand on authorized.by."New value: +"Number of retailers with a public, approved profile that this brand currently authorizes on authorized.by. Only authorizations confirmed by both the brand and the retailer count; pending requests and ended authorizations do not."
  2. Changed1 schema field changed
    • changedInput schema / properties / search / description
      Previous value: -"Filter by brand name or alias. Optional."New value: +"Filter by brand name, alias or website domain/URL, e.g. 'deuter' or 'deuter.com'. Optional."
  3. Changed2 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "description": "A page of brands plus network-wide totals and pagination.",
      +  "properties": {
      +    "brands": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "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"
      +            ]
      +          },
      +          "retailer_count": {
      +            "description": "Number of retailers currently authorized by this brand on authorized.by.",
      +            "type": "integer"
      +          },
      +          "slug": {
      +            "description": "URL-safe identifier. Accepted by the id_or_alias argument of the detail tools.",
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "name",
      +          "slug",
      +          "logo",
      +          "retailer_count"
      +        ],
      +        "type": "object"
      +      },
      +      "type": [
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "meta": {
      +      "additionalProperties": false,
      +      "description": "Network-wide totals.",
      +      "properties": {
      +        "generated_at": {
      +          "description": "Timestamp (ISO 8601) the index was generated.",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "total_brands": {
      +          "description": "Total number of public brands on authorized.by.",
      +          "type": "integer"
      +        },
      +        "total_connections": {
      +          "description": "Total number of active brand-retailer authorizations on authorized.by.",
      +          "type": "integer"
      +        },
      +        "total_retailers": {
      +          "description": "Total number of public retailers on authorized.by.",
      +          "type": "integer"
      +        }
      +      },
      +      "required": [
      +        "total_brands",
      +        "total_retailers",
      +        "total_connections",
      +        "generated_at"
      +      ],
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "pagination": {
      +      "additionalProperties": false,
      +      "description": "Pagination of this response.",
      +      "properties": {
      +        "page": {
      +          "description": "Zero-based page number of this response.",
      +          "type": "integer"
      +        },
      +        "size": {
      +          "description": "Page size used for this response.",
      +          "type": "integer"
      +        },
      +        "total_items": {
      +          "description": "Total number of matching entries across all pages.",
      +          "type": "integer"
      +        },
      +        "total_pages": {
      +          "description": "Total number of pages.",
      +          "type": "integer"
      +        }
      +      },
      +      "required": [
      +        "page",
      +        "size",
      +        "total_items",
      +        "total_pages"
      +      ],
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "brands",
      +    "meta",
      +    "pagination"
      +  ],
      +  "type": "object"
      +}
  4. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, and the description adds real context on top: the data scope is limited to relationships confirmed on authorized.by, and an empty result does not prove no authorization exists elsewhere. The error taxonomy distinguishing empty list, not-found and technical failure is exactly the kind of behavioral detail annotations cannot carry.

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?

Front-loaded with purpose and search semantics before the caveats, and the outcome-distinction sentence is dense but earns its place. 'Read-only' duplicates the readOnlyHint annotation and the return-field list is partly redundant with the output schema, costing a little tightness.

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 three-optional-parameter read tool with an output schema and full annotation coverage, nothing an agent needs is missing: scope limits, pagination, match semantics and error interpretation are all present.

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%, so page, size and search are already documented, including the partial-match behavior and the 500 maximum. The description adds only the 'omit search to get the full index' framing, which is useful but largely restates the optionality the schema already encodes.

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 ('Search brands (manufacturers) registered on authorized.by') plus the list-all mode, which separates it from a single-record lookup. It never names the sibling get_brand, so the boundary with single-brand retrieval is left implicit.

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?

Explicitly says to omit 'search' for the full index and to use 'page'/'size' for pagination, and it explains how to interpret empty results versus 'Brand not found' versus 'Tool execution failed'. It stops short of routing to alternatives such as get_brand for a known id.

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