AI agents call search_advertisers to retrieve information from Pipiads without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
sort | number | Yes | Sort: 0=Ad count, 1=Plays, 2=Likes, 4=Days, 6=Cost USD, 7=Start date, 8=End date, 10=Monthly visits, 13=Est orders, 14=Ad count |
time | number | Yes | Time range: 3=All, 4=Yesterday, 0=7d, 1=30d, 2=90d |
region | array | — | Country/region codes |
ad_type | number | — | Ad type filter |
cpa_max | number | — | Maximum CPA |
cpa_min | number | — | Minimum CPA |
cpm_max | number | — | Maximum CPM |
cpm_min | number | — | Minimum CPM |
keyword | string | — | Search keyword (shop name or URL) |
ad_state | number | — | Ad state: 1=Active, 0=Stopped |
data_type | number | Yes | Platform: 0=All, 1=TikTok, 2=Facebook, 3=Meta Library |
page_size | integer | Yes | Results per page |
Parameters from the server's own tool schema.
This tool retrieves and filters advertising intelligence data from a leaderboard. It performs a query operation that returns information without creating, modifying, deleting, executing code, or moving money. The filtering parameters are all informational (platform, region, metrics, visits) suggesting passive lookups.
From the tool's definition Tool description explicitly states 'Search advertiser leaderboard' with filtering capabilities (platform, region, ad metrics, monthly visits).
Risk signalsHigh parameter count (37 properties)
Attacks that exploit this kind of access
Search advertiser leaderboard. Filter by platform, region, ad metrics, monthly visits. It is categorised as a Read tool in the Pipiads MCP Server, which means it retrieves data without modifying state.
search_advertisers accepts 12 parameters: sort, time, region, ad_type, cpa_max, cpa_min, cpm_max, cpm_min, keyword, ad_state, data_type, page_size. Required: sort, time, data_type, page_size. The full parameter table on this page comes from the server's own tool schema.
Register the Pipiads MCP server in PolicyLayer and add a rule for search_advertisers: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Pipiads. Nothing to install.
search_advertisers is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the search_advertisers rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for search_advertisers. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
search_advertisers is provided by the Pipiads MCP server (pipiads-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →