Skip to main content
Glama

Search nutra & crypto affiliate offers

search_affiliate_offers
Read-only

PAID ADD-ONS «Nutra» and «Crypto», sold separately (MCP comes with the annual plan of each vertical). Find Meta ads whose landing pages are nutra or crypto affiliate offers, filtered by vertical (lp_category), niche (lp_subcategory), offer (lp_product), celebrity the landing page features (lp_celebrity — names as returned by get_affiliate_celebrities), text (q) and Facebook launch date (date_from/date_to). PAGING: one call returns at most 50 rows; when has_more=true, repeat the call with the same filters and cursor=next_cursor to get the next page (new rows, never the same ones) — keep following next_cursor until has_more=false. total is the exact number of matching ads and is omitted when no exact count is available (absent total never means zero). Each row: ad_id, advertiser, landing_domain, vertical, niche, offer. Without the add-on the call is refused; a monthly «site» subscriber is told that MCP access is part of the annual plan. QUOTA: 1 MCP credit per delivered row; section rows have their own allowance — up to 500 rows per UTC day and 5 000 per UTC month per account, shared by every tool (search_ads, get_ad, get_media and the rest count the Nutra / Crypto / Web2App rows they return too), which MCP credit packs do not raise; market summaries (get_web2app_market) are outside it. PRICING: on paid plans ×1 after 500 MCP credits/month; one-time consent via accept_pricing_terms; before calling, get the maximum debit from estimate_cost (free) and tell the user.

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": "search_affiliate_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNofree-text search in the ad
limitNorows per page, 1-50 (default 20); page further with cursor
cursorNonext_cursor of the previous response with the same filters: returns the next page
date_toNoFacebook launch date on/before, YYYY-MM-DD
date_fromNoFacebook launch date on/after, YYYY-MM-DD
lp_productNooffer (product) name as shown by this tool (OR)
lp_categoryNovertical: nutra_affiliate or crypto_affiliate (OR); omitted = the verticals your annual plans open
lp_celebrityNocelebrity name exactly as returned by get_affiliate_celebrities: ads whose landing pages feature this person (OR)
lp_subcategoryNoniche as vertical/niche, e.g. nutra_affiliate/weight_loss (OR)

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNoPresent only when isError is true: machine-readable failure. The human explanation stays in content.
totalNo
paramsNoRequest parameter echo: applied = parameters that shaped this result; normalized = parameters rewritten before applying (alias, type coercion, resolved id); ignored = parameters that were accepted but NOT applied, with the reason.
degradedNo
has_moreNo
addon_hintsNoAdd-on modules that have additional data for objects of this result (no prices, no paid values). subscription_status=active: the account has the module — use its normal path. Do not push a purchase the user did not ask about.
next_cursorNo
degraded_reasonNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / degraded
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / degraded_reason
      Added value: +{
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / properties / lp_celebrity
      Added value: +{
      +  "description": "celebrity name exactly as returned by get_affiliate_celebrities: ads whose landing pages feature this person (OR)",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": [
      +    "null",
      +    "array"
      +  ]
      +}
  3. Changed5 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "next_cursor of the previous response with the same filters: returns the next page",
      +  "type": "string"
      +}
    • addedInput schema / properties / date_from
      Added value: +{
      +  "description": "Facebook launch date on/after, YYYY-MM-DD",
      +  "type": "string"
      +}
    • addedInput schema / properties / date_to
      Added value: +{
      +  "description": "Facebook launch date on/before, YYYY-MM-DD",
      +  "type": "string"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"rows to return, 1-50 (default 20)"New value: +"rows per page, 1-50 (default 20); page further with cursor"
    • addedOutput schema / properties / next_cursor
      Added value: +{
      +  "type": "string"
      +}
  4. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnly/destructiveHint=false, but the description goes well beyond them: refusal behavior for non-entitled accounts, a 1-credit-per-row billing model, exact quota limits shared with other tools, the >500-credit pricing multiplier, and the semantic quirk that an absent total does not mean zero. It also lists the returned row fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core purpose is buried behind an all-caps add-on gate and then buried again under PAGING, QUOTA and PRICING blocks in a single dense paragraph. Nearly every fact is useful, but the wall-of-text layout with heavy capitalization makes it harder to front-load the primary selection signal.

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 gated, quota-metered, paginated search tool this covers everything an agent needs: entitlement, pagination loop (follow next_cursor until has_more=false), cost estimation, consent, quota ceilings, and returned row shape. An output schema plus annotations exist, so return-value detail is appropriately not exhaustive.

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 description coverage is 100%, so the baseline is 3; the description largely restates what the schema already documents (lp_category verticals, lp_celebrity names from get_affiliate_celebrities, OR semantics, date range as Facebook launch date). It adds only marginal meaning, such as explaining that lp_category omission falls back to the verticals the annual plans unlock.

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?

"Find Meta ads whose landing pages are nutra or crypto affiliate offers" is a precise verb+resource with an explicit scope (affiliate landing pages, not ads generally), and the filter dimensions are enumerated. It does not explicitly name search_ads as the tool for non-affiliate ad search, so the sibling boundary is only implied by the vertical restriction and the add-on gating.

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?

States concrete preconditions and exclusions: the call is refused without the add-on, monthly site subscribers are rejected, estimate_cost must be called first to get the max debit, and accept_pricing_terms gives one-time consent. Quota ceilings (500/day, 5,000/month, shared across tools) and paging continuation rules are spelled out, leaving little to inference.

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.