Spytrend

Find related ads

find_similar_ads

Read-only

Find ads related to one source ad by an explicit overlap basis: fanpage (same Facebook page_id) or domain (same exact landing_domain). This is entity overlap, NOT visual similarity of the material; use find_similar_creatives for that. The source ad is excluded from data, but pagination.total remains the upstream overlap-candidate count before that exclusion; source_excluded and total_semantics make this explicit instead of fabricating an adjusted exact total. Metadata only, cursor-paginated. QUOTA: 1 token per delivered row (default page 20).

Input Schema

TableJSON Schema

Name	Required	Description
`ad_id`	Yes	source ad UUID from search_ads
`basis`	Yes	overlap basis: fanpage (same Facebook page_id) or domain (same exact landing_domain)
`limit`	No	maximum metadata rows (default 20, maximum 200; 1 token per delivered row)
`cursor`	No	pagination cursor returned by the previous call

Output Schema

TableJSON Schema

Name	Required	Description	Default
`data`	Yes
`pagination`	Yes
`basis_value`	Yes
`source_ad_id`	Yes
`source_excluded`	Yes
`total_semantics`	Yes
`similarity_basis`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedSep 10, 2026

addedOutput schema / properties / data / items / properties / creative_destination_domain
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / data / items / properties / creative_destination_url
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / data / items / properties / is_multilang
```
Added value: +{
+  "type": [
+    "null",
+    "boolean"
+  ]
+}
```
addedOutput schema / properties / data / items / properties / media / items / properties / body
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / data / items / properties / media / items / properties / carousel_position
```
Added value: +{
+  "type": [
+    "null",
+    "integer"
+  ]
+}
```
addedOutput schema / properties / data / items / properties / media / items / properties / claimed_domain
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / data / items / properties / media / items / properties / cloaking_detected
```
Added value: +{
+  "type": "boolean"
+}
```

addedOutput schema / properties / data / items / properties / media / items / properties / fallback_urls

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": [
+    "null",
+    "array"
+  ]
+}

addedOutput schema / properties / data / items / properties / media / items / properties / is_alive
```
Added value: +{
+  "type": [
+    "null",
+    "boolean"
+  ]
+}
```
addedOutput schema / properties / data / items / properties / media / items / properties / link_url
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / data / items / properties / media / items / properties / title
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / data / items / properties / opening_price

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "billing_basis": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    },
+    "tokens": {
+      "type": [
+        "null",
+        "integer"
+      ]
+    },
+    "unit": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "status",
+    "tokens",
+    "unit",
+    "billing_basis"
+  ],
+  "type": [
+    "null",
+    "object"
+  ]
+}

addedOutput schema / properties / data / items / properties / original_landing_domain
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / data / items / properties / primary_creative

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "body": {
+      "type": "string"
+    },
+    "carousel_position": {
+      "type": [
+        "null",
+        "integer"
+      ]
+    },
+    "claimed_domain": {
+      "type": "string"
+    },
+    "cloaking_detected": {
+      "type": "boolean"
+    },
+    "expiring": {
+      "type": "boolean"
+    },
+    "fallback_urls": {
+      "items": {
+        "type": "string"
+      },
+      "type": [
+        "null",
+        "array"
+      ]
+    },
+    "is_alive": {
+      "type": [
+        "null",
+        "boolean"
+      ]
+    },
+    "link_url": {
+      "type": "string"
+    },
+    "media_type": {
+      "type": "string"
+    },
+    "snapshot_url": {
+      "type": "string"
+    },
+    "thumbnail_url": {
+      "type": "string"
+    },
+    "title": {
+      "type": "string"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "type": [
+    "null",
+    "object"
+  ]
+}

addedOutput schema / properties / data / items / properties / primary_creative_selection

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "carousel_position": {
+      "type": [
+        "null",
+        "integer"
+      ]
+    },
+    "reason": {
+      "type": "string"
+    },
+    "status": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "status"
+  ],
+  "type": [
+    "null",
+    "object"
+  ]
+}

First observedSep 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, it reveals the source ad exclusion, the pagination.total semantics, the existence of source_excluded and total_semantics fields, and the quota cost per row. This added context explains edge cases an agent might otherwise misinterpret.

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?

The description is dense and information-rich, with each sentence serving a purpose (purpose, distinction, output semantics, quota). It is slightly verbose but well-structured and front-loaded with the core action.

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?

Given the tool's complexity (pagination, output schema, annotations), the description covers behavioral quirks, quota, and alternative tools. It fully compensates for anything not obvious from the schema or annotations, making it complete for an agent.

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% and the description adds little beyond the schema for parameters. It does reinforce the meaning of basis, but the schema already describes all parameters adequately; no new parameter-level insight is provided.

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?

The description clearly states the verb (find) and resource (ads related to one source ad) with an explicit overlap basis (fanpage or domain). It distinguishes itself from visual similarity tools by directly naming find_similar_creatives, making the purpose unambiguous.

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?

It explicitly states when to use (entity overlap on fanpage/domain) and when not to (not visual similarity) along with the alternative tool. This gives clear selection guidance relative to siblings without any ambiguity.

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.