Spytrend

Get creative media (download URLs)

get_media

Read-only

Fetch downloadable creative MEDIA (image/video URL + thumbnail) for 1-500 ad or creative UUIDs returned by search_ads / search_creatives. This is the paid delivery step. entity_type is 'ad' or 'creo'. Existing clients keep the {entity_type,items:[{id,media:[{media_type,url,thumbnail_url,fallback_urls}]}]} fields; additive counts, partial and failures explain malformed, quota-limited and unavailable items, plus interrupted items when at least one peer was delivered. Malformed/zero UUIDs never reach the API or consume quota; valid peers in a mixed batch are still processed. duplicate_count reports canonical duplicates, which are fetched and billed once. IMPORTANT: a media URL can become unavailable, so if url returns an HTTP error (e.g. 416/404), retry fallback_urls in order before treating it as unavailable. Typical flow: search_ads (browse metadata, 1 token per row) → pick ids → get_media. QUOTA: 50 tokens per delivered multilang-upload ad, 1 per ordinary ad, 10 per creative-catalogue item (free starter: 500 tokens total; paid plans: 40,000/month). The ad price is per returned ad, not per media file. Actual ad membership determines the price even without a preceding filtered search. Every new call is billed; get_ad already includes media, so do not call get_media again for files you already received. Invalid, missing or undelivered items are not charged. Mixed batches examine a quota-bounded prefix and return affordable items with explicit failures for the rest; an unexamined tail may contain affordable ordinary ads, which can be requested separately. get_usage is free. MULTILANG CONTENT: get_ad and get_media(ad) use the same full detail carousel. primary_creative identifies its selected first creative; primary_creative_selection.status describes selected, fallback or unavailable. carousel_position is the original 1-based carousel position, not the returned array index. Missing/unconfirmed selected primary media is not charged or disclosed; both tools report primary_creative_unavailable. Per-slide title/body/link_url describe that slide; when the API omits a slide override, the ad-level value is supplied as its fallback, consistently in both tools. original_landing_domain describes the original ad, while creative_destination_url/domain describe the primary creative's destination. cloaking_detected is a detected domain/copy mismatch, not a verified redirect or a guarantee that a creative is black. Actual per-call debit is reported in _meta.billing.tokens_charged, in Spytrend quota tokens (not model tokens); admin may be exempt.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ids`	Yes	1 to 500 ad or creative UUIDs to resolve (from search_ads / search_creatives results); malformed ids are reported per item and never consume quota
`entity_type`	Yes	what kind of media to fetch: 'ad' (creative media of ads from search_ads) or 'creo' (media of creatives from search_creatives)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes
`partial`	Yes
`failures`	No
`entity_type`	Yes
`valid_count`	Yes
`attempted_count`	Yes
`delivered_count`	Yes
`duplicate_count`	Yes
`requested_count`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed16 schema fields changedSep 10, 2026

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

addedOutput schema / properties / items / 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 / items / items / properties / original_landing_domain
```
Added value: +{
+  "type": "string"
+}
```

addedOutput schema / properties / items / 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 / items / 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.5/5.0

Behavior5/5

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

Adds substantial behavior beyond the annotations: quota token costs, per-item failure handling, mixed-batch prefix processing, duplicate handling, fallback_urls retry on HTTP errors, and multilang content behavior. It even explains what happens to malformed/zero UUIDs. No contradiction with the readOnlyHint/destructiveHint annotations.

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 description is thorough but extremely long and dense, with many details that duplicate the output schema, such as the response fields block. It is front-loaded with the core purpose, but it would benefit from bullets or sectioning to improve scanability. While much of the content is valuable, it is not concise.

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?

Covers an unusually complete set of edge cases: quota billing, partial failures, mixed batches, fallback URLs, duplicate items, multilang selection, and pricing rules. Given the output schema exists, nothing critical appears missing for an agent to correctly select, invoke, and interpret the results of this paid endpoint.

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?

The input schema already documents both parameters with 100% coverage, including the entity_type enum and the ids array limits. The description adds operational context such as billing and malformed-id handling, but it does not meaningfully enrich the semantic meaning of the parameters beyond what the schema already provides, so the baseline score of 3 applies.

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 action and resource: 'Fetch downloadable creative MEDIA (image/video URL + thumbnail) for 1-500 ad or creative UUIDs returned by search_ads / search_creatives.' It also says it is the 'paid delivery step,' which gives an immediate sense of why this tool exists and how it differs from free browsing tools. It distinguishes itself from get_ad by warning against duplicate fetching.

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?

Provides an explicit typical flow: 'search_ads ... → pick ids → get_media.' It also gives clear exclusion guidance: 'get_ad already includes media, so do not call get_media again for files you already received,' and notes 'get_usage is free.' This is strong when-to-use and when-not-to-use guidance.

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.