Spytrend

Celebrities of nutra & crypto affiliate landings

get_affiliate_celebrities

Read-only

PAID ADD-ONS «Nutra» and «Crypto», sold separately (MCP comes with the annual plan of each vertical). Celebrities that nutra and crypto affiliate landing pages build their pitch on (endorsement, fake news story, interview, quote; plain mentions are not counted) — the same list as the «What's inside» block of the vertical on spytrend.com. Each row: name, role (how the pages present the person), ads (ads of the selection featuring them; an ad with several people counts for each), sites, share of the selection's ads, example_ad_id. Filters: vertical (lp_category), niche (lp_subcategory), Facebook launch date (date_from/date_to), q over name and role; most ads first, limit up to 200, total_celebrities counts every match. To list the ads of a person call search_affiliate_offers with lp_celebrity= and the same vertical. 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 call; summaries are not limited by the section row allowance. 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": "get_affiliate_celebrities"
  }
}

Input Schema

Name	Required	Description
`q`	No	keep only people whose name or role contains this text
`limit`	No	people to return, 1-200 (default 50), most ads first
`date_to`	No	count ads launched on Facebook on/before, YYYY-MM-DD
`date_from`	No	count ads launched on Facebook on/after, YYYY-MM-DD
`lp_category`	No	vertical: nutra_affiliate or crypto_affiliate (OR); omitted = the verticals your annual plans open
`lp_subcategory`	No	niche as vertical/niche, e.g. nutra_affiliate/weight_loss (OR)

Output Schema

Name	Required	Description
`data`	No
`note`	No
`error`	No	Present only when isError is true: machine-readable failure. The human explanation stays in content.
`scope`	No
`params`	No	Request 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.
`pending`	No
`total_ads`	No
`verticals`	No
`addon_hints`	No	Add-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.
`total_celebrities`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the bar is lower. The description still adds substantial non-schema context: add-on gating and refusal behavior, the monthly-subscriber message, 1 MCP credit per call, and the ×1 multiplier after 500 credits/month. It does not describe pagination or ordering edge cases, but the paywall and cost disclosure is well beyond what annotations carry.

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 — inclusion criteria, row shape, filters, cross-references, paywall, quota, pricing — with no filler. However, it is delivered as one dense run-on block of semicolon-separated clauses rather than front-loading the core purpose ahead of the add-on/commercial preamble, which slows scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 6-parameter, zero-required tool with an output schema, the description covers purpose, filtering, sorting, limit ceiling, match counting, and the prerequisite consent/cost flow, so an agent can call it correctly. Minor gaps remain around what happens on invalid vertical values or whether an exact-name miss returns empty versus an error.

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 coverage is 100%, so every parameter is already documented inline, establishing a baseline of 3. The description adds a useful mapping of friendly filter names to parameter keys (vertical→lp_category, niche→lp_subcategory, Facebook launch date→date_from/date_to) and notes q searches name and role, but most of that restates the schema's own descriptions.

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 resource (celebrities used in nutra and crypto affiliate landing pitches) with a precise inclusion rule — endorsement, fake news story, interview, quote — and explicitly excludes plain mentions. It also enumerates the returned row fields, so the agent knows exactly what the tool yields versus siblings like get_influencer or search_influencers.

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 explicit routing: to get a person's ads, call search_affiliate_offers with lp_celebrity set to the exact returned name plus the same vertical. It also states the prerequisite (the paid add-on) and the refusal behavior without it, which tells the agent when the call cannot succeed at all.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Spytrend tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.