Skip to main content
Glama

Spytrend

by com.spytrend

Get creative details and breakdown by id

get_creative
Read-only

Fetch ONE creative's metadata plus its canonical bounded breakdown by id: activity period/quality, max_days_active with max_days_active_source/max_days_active_quality, delivery_languages with explicit legacy provenance, aggregate counts, advertisers, fanpages, landing domains, webmasters and geos. The ambiguous legacy languages alias is intentionally omitted. When a speech transcript has already been generated for a video, copy_languages is returned separately with copy_language_source=cached_asr_transcript and copy_language_scope=spoken_audio; it describes spoken audio only, not title/body or visual OCR. copy_language_status is available for measured confidence >=0.8, available_low_confidence below that, available_unscored when the provider supplied no probability, and unavailable when there is no valid cached result. This read never starts transcription. Breakdown lists are sorted by ad count desc and capped at 1000 rows; each dimension has its own *_status, _returned and (where a snapshot cardinality exists) _count/_truncated/_count_status. breakdown_status is available_bounded only when every dimension query completed, partial when at least one dimension is unavailable, and unavailable when the breakdown endpoint itself failed. The id is a creative UUID from search_creatives. Media URLs are intentionally excluded; download with get_media (entity_type=creo, same id). Fanpage ids feed the search_creatives fanpages filter and search_ads page_id. QUOTA: 1 token (one entity card).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesthe resource id to fetch

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, and the description substantially extends this with behavioral detail: canonical bounded breakdown, omission of the ambiguous legacy languages alias, copy_languages provenance and scope, breakdown status semantics, sorting/capping at 1000 rows, per-dimension status fields, and the explicit statement that this read never starts transcription. No contradiction with annotations exists.

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

Conciseness5/5

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

Although long, the description is front-loaded with the core purpose and every subsequent clause carries operational meaning: statuses, sorting, truncation, provenance, exclusions, and quota. There is no redundant filler or repetition of schema or annotation content.

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 single-parameter read tool with a full output schema, the description covers the essential context: how to obtain the id, what data is included and excluded, how to route to get_media, breakdown status conditions, quota cost, and behavioral guarantees like no transcription. Nothing critical is left unresolved.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema only says id is 'the resource id to fetch,' while the description adds crucial meaning: it is a creative UUID from search_creatives, the same id used for get_media with entity_type=creo, and it selects a single creative. This is meaningful value beyond the schema's generic description.

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 opens with a specific verb and resource: 'Fetch ONE creative's metadata plus its canonical bounded breakdown by id.' It clearly distinguishes this from search_creatives by emphasizing a single id lookup rather than search, and it names the id provenance as a creative UUID from search_creatives.

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?

The description gives explicit routing guidance: it tells the agent to use get_media for media URLs with entity_type=creo and the same id, and states that fanpage ids feed the search_creatives fanpages filter and search_ads page_id. It also clarifies this tool never starts transcription, preventing misuse for transcript generation.

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

All Spytrend toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool pairs a distinct action verb with a distinct entity type: search_* queries databases, get_* fetches single-entity cards, find_similar_* performs similarity lookups, and add_to_favorites/list_favorites handle saved items. The three find_similar tools explicitly cross-reference their differences (visual vs entity overlap vs URL-parameter), and get_adversus search_advertisers are clearly single-card vs typeahead.

Naming Consistency5/5

All 21 tools follow a consistent verb_noun snake_case pattern: six search_* tools, ten get_* tools, three find_similar_* tools, plus add_to_favorites and list_favorites. No camelCase, no mixed verb styles, and the similarity trio shares an identical prefix, making the set highly predictable.

Tool Count4/5

At 21 tools this is above the typical 3-15 sweet spot, but the server spans six entity domains (ads, creatives, advertisers, webmasters, hubs, shops) plus cross-cutting media delivery, favorites, trends, analytics, similarity and usage. Nearly every tool maps to a distinct workflow step, so the set feels dense rather than bloted.

Completeness4/5

The core lifecycle is fully covered: search every entity type, fetch detail cards, download media, save to favorites, list favorites back, plus trends, analytics, similarity and TikTok surfaces. The main gaps are a remove_from_favorites operation and a standalone hub detail card, neither of which blocks the primary ad-intelligence workflows.

Resources