Skip to main content
Glama

Find ads

sightglass_find_ads
Read-onlyIdempotent

Search a library of real Meta ads and the landing pages they drive to. search is a semantic vector search, so describe the ad's angle, offer or visual style rather than one keyword. Combine it with companyIds, displayFormats, pageTypes and technologies to narrow, and with hookTypes, angleTypes, offerTags and funnelStages to filter on what the ad's creative was read as (each ad carries these in tags, null until it is read). Users say 'brands' for advertisers and 'landing pages' for site pages — map their words onto these filters. performanceScore and scoreTiers come from a transparent longevity + duplication heuristic; they are NOT spend, reach or ROAS and must never be presented as such. Returns metadata plus ready-to-view media URLs; call sightglass_get_ad for one ad's full detail, sightglass_get_site_page for the page an ad drives to. 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 search over the ad's copy, creative caption and advertiser. Describe the angle, offer or visual style you want (for example 'before and after skin results with a discount code'), not a single keyword.
statusNo
hookTypesNoCSV of hook types: question,bold_claim,problem_callout,curiosity,proof_number,before_after,first_person_story,offer_first,us_vs_them,demo,audience_callout,contrarian,customer_testimonial,expert_or_celebrity,new_or_launch,product_showcase
offerTagsNoCSV of offer tags: discount,bundle,subscription,trial_or_sample,gift_with_purchase,financing,free_shipping,giveaway
pageTypesNoCSV of landing-page types: offer_page,advertorial,listicle,quiz,lead_capture,homepage,pdp,collection,blog,marketplace,app_store,social_profile. The stored names product, squeeze and other still work.
projectIdNoReplo project id, from list_projects: where the charge or the asset lands. Its workspace's plan applies.
angleTypesNoCSV of angle types: problem_solution,mechanism,proof,comparison,identity,founder_story,objection_handling,urgency,education,transformation,price_or_value,quality_or_craft,clean_or_non_toxic,convenience,gifting,sustainability
companyIdsNoCSV of company ids. Users usually call companies 'brands'.
scoreTiersNoCSV of testing,scaling,growing,optimized,winning. These tiers come from a transparent longevity + duplication heuristic — they are NOT spend, reach or ROAS, and must never be described as such.
workspaceIdNoReplo workspace id, from list_workspaces. Sets which workspace's plan applies; required when the user has more than one workspace.
funnelStagesNoCSV of funnel stages: cold,warm,retargeting
technologiesNoCSV of stack names on the brand's site, e.g. Shopify,Klaviyo
displayFormatsNoCSV of image,video,carousel,dco,dpa,text,other

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description goes well beyond them: performanceScore/scoreTiers are a longevity+duplication heuristic, NOT spend/reach/ROAS; plan-gated fields return null and are listed in `locked`; lockedCount signals more results on a higher plan; the tool returns data only and nothing is shown until sightglass_show is called.

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?

Purpose is front-loaded and most sentences carry unique operational information, but it is a dense single block with mild redundancy (the 'not spend, reach or ROAS' caveat appears twice, and the plan-locked explanation is split across two clauses). Slightly tighter grouping would help an agent parse it.

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?

With 16 optional params, no output schema, and no required fields, the description covers what is needed: what comes back (metadata + media URLs), pagination via cursor, the resultId → sightglass_show handoff, and the plan-gating behavior. An agent can call it correctly 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 already 88%, so the schema carries most of the parameter semantics. The description still adds real value by explaining the semantics of `search` (vector search over copy, caption, advertiser), translating user vocabulary onto companyIds/pageTypes, and warning that scoreTiers/performanceScore are heuristic, not ad spend.

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?

Opens with a specific verb+resource: searching a library of real Meta ads and the landing pages they drive to. It further distinguishes itself from siblings by naming sightglass_get_ad and sightglass_get_site_page as the single-item lookups, and from sightglass_find_site_pages as the ad-side search.

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 guidance on how to phrase `search` (semantic, describe angle/offer/visual style, not one keyword), which filter groups do what (narrow vs. creative-read tags), vocabulary mapping ('brands' → companyIds, 'landing pages' → pageTypes), and the follow-up workflow: call sightglass_show with resultId once you know the answer, and it can be called 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