Skip to main content
Glama

find_brand

Find a competitor by name or shop domain, before get_brand or brand_changes. Use it whenever the user names a brand or store ('show me Epycure's ads', 'what is Leaf running', 'gymshark.com'). Fuzzy: returns up to 10 confirmed e-commerce brands, best first, each with what matched (page name or shop domain), its page_id, shop link, and how many ads, winners and active ads Poseidon holds. No search of people's names: a page named after a person is found by its shop domain only. Free.

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": {
      "q": "<q>"
    },
    "name": "find_brand"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesbrand name or shop domain, e.g. 'epycure' or 'leaf-cosmetics.com'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations present the description carries the full burden, and it discloses a lot: fuzzy matching, a hard cap of 10 results, best-first ordering, the exact fields returned per match (page_id, shop link, ad/winner/active counts), and that the call is free. It stops short of saying what happens on zero matches or how ambiguous partial names are resolved, which are the remaining behavioral 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?

Front-loaded with the routing decision first, then examples, then return semantics, then constraints. It is dense and slightly fragment-heavy with parentheticals, but nearly every clause carries operational value and nothing is padding.

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?

There is no output schema, and the description compensates by enumerating the returned fields and ordering, so an agent knows exactly what it gets back. Combined with the usage conditions and the single well-documented parameter, nothing critical is missing for a lookup tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so the baseline is 3; the description goes beyond it by constraining the input to e-commerce brands and adding that a page named after a person can only be matched via its shop domain, which meaningfully shapes how the agent should format q.

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?

States a specific verb and resource ('Find a competitor by name or shop domain') and explicitly positions it ahead of sibling tools (get_brand, brand_changes), so an agent can route correctly without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit trigger ('Use it whenever the user names a brand or store'), concrete example utterances, the sequencing relative to downstream tools, and a clear exclusion ('No search of people's names'). When-to-use, when-not, and what comes next are all covered.

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