Skip to main content
Glama

get_brand

What one brand or shop is running on Meta. Use it when the user names a store or brand ('what is epycure.com running', 'how long do Leaf Co's ads last'). Give the shop domain (e.g. epycure.com) or the Meta page id. Returns the shop (link, platform), the brand's ads in Poseidon by format, how many are winners, the median days live (when 30+ ads), its 10 longest-running ads with reach, links and verbatim hooks, and its A/B tests with a measured outcome. Poseidon reads up to 30 ads per brand page. Costs 5 credits.

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_brand"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNothe shop's website, e.g. epycure.com
page_idNoMeta page id, if known

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses the data cap ('reads up to 30 ads per brand page'), a conditional computation ('median days live when 30+ ads'), the full return payload, and an explicit cost ('Costs 5 credits'). Those are exactly the operational caveats an agent needs before spending budget.

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-loads the purpose, then usage, then inputs, then returns and cost in a sensible order with zero filler. The return-value enumeration is long but each item is informative, so it earns its space.

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?

No output schema exists, so the description must describe returns and it does thoroughly (shop link/platform, ads by format, winners, median days live, top 10 with reach/hooks, A/B outcomes). Combined with the input guidance, cost, and coverage limit, nothing needed to call it correctly is missing.

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 both fields are documented, but the description adds the crucial either/or semantics ('give the shop domain ... or the Meta page id') that the schema alone does not convey given required=0. It clarifies that one identifier suffices, exceeding the baseline for a fully documented 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?

States a specific verb+resource ('what one brand or shop is running on Meta') and pins the scope to a single entity, which separates it from search-style siblings like find_brand without needing to name them. The quoted example queries make the unit of retrieval unambiguous.

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?

Gives concrete when-to-use triggers ('Use it when the user names a store or brand') with two realistic example utterances, plus how to supply the identifier. It stops short of naming an alternative for multi-brand or keyword searches, so the agent must infer that boundary.

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