Skip to main content
Glama

Search brands

sightglass_search_companies
Read-onlyIdempotent

Search Sightglass companies — what users call brands: the business behind one or more Meta advertiser pages, keyed on its domain. search is semantic, so describe the business (what it sells and to whom). Pass similarToCompanyId to find a company's nearest competitors instead. To look a brand up by its website pass domainSearch; when that finds nothing the brand is not tracked yet, so read its site or use the user's words, write one sentence on what it sells and to whom, and pass that as search: the results are tracked brands competing for the same customers. Each result carries store facts (platform, estimated monthly sales, products, employees, follower counts with 30-day change — all vendor estimates, never reported revenue), rank and rank movement by active ads, and momentum: a transparent 0-100 score whose components[].text say why a brand is growing (ad launches vs last month, active-ad change, follower growth, catalog activity, stack upgrades). Sort by momentum for who is blowing up, most_estimated_sales for the biggest, most_active_ads for who is spending. Trends come from ad start/stop dates and only cover ads Sightglass has seen. Fields the user's Replo plan doesn't include come back null and are named in that item's locked list (estimates = sales, visits and traffic); lockedCount is how many more results a higher plan shows. Say the data is on a higher plan; never estimate it yourself. Returns data only: nothing is shown to the user yet. Once you know the answer, call sightglass_show once with this call's resultId to show it as cards; the show call does not search again. Works without a Replo account: call it before asking the user to sign in.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNo
limitNoResults per page: 20 by default, up to 40. Use the user's number when they give one; for more than 40, page with cursor.
cursorNonextCursor from the previous page of this same call, to get the next page. Keep every other argument the same.
searchNoSemantic by default: describe the business (what it sells, to whom), not one keyword.
projectIdNoReplo project id, from list_projects: where the charge or the asset lands. Its workspace's plan applies.
searchModeNo
categoryIdsNoCSV of category ids from sightglass_search_companies results; a node matches its whole subtree.
workspaceIdNoReplo workspace id, from list_workspaces. Sets which workspace's plan applies; required when the user has more than one workspace.
domainSearchNoA brand's website, e.g. example.com or a full URL, to find that brand when Sightglass tracks it.
activeAdsCountGteNo
similarToCompanyIdNoFind the nearest competitors of this company instead of searching.

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?

Goes well past the annotations by disclosing that metrics are vendor estimates and never reported revenue, that trends only cover ads Sightglass has seen, that plan-gated fields return null and appear in locked/lockedCount, and that nothing is displayed to the user until sightglass_show is called. The remaining gap is minor: it doesn't state result/page size behavior beyond the schema's cursor note.

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?

Every sentence carries information and the purpose is front-loaded ahead of the workflow and caveats. It is, however, a single dense paragraph of ~290 words with several distinct ideas (modes, sort guidance, plan gating, show workflow) that would be easier to scan if segmented.

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 an 11-parameter, no-output-schema search tool, the description compensates for the missing return contract by enumerating what each result carries (store facts, rank movement, momentum components) and how the resultId drives sightglass_show. An agent has enough to search, interpret, and present results without further context.

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 73%, and the description adds real meaning for the highest-risk parameters: search is semantic (describe business and audience, not a keyword), similarToCompanyId substitutes for a search, and domainSearch is a website lookup with a defined failure mode. It explains only 3 of the 10 sort values and never mentions searchMode, so it stops short of full coverage.

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 (search) and resource (Sightglass companies), then disambiguates the terminology an agent would otherwise guess at: a company is the business behind one or more Meta advertiser pages, keyed on domain. This cleanly separates it from sibling readers like sightglass_get_company and sightglass_research_company.

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?

Explicit routing rules: use similarToCompanyId for nearest competitors instead of searching, use domainSearch for a known website, and a named fallback when domainSearch returns nothing (read the site, write one sentence, pass it as search). It also names the downstream show step and states the tool works before sign-in.

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