Spytrend

Get influencer card

get_influencer

Read-only

Fetch one creator card from the influencer directory by platform (youtube or instagram) and slug (as returned by search_influencers). Same fields as a search row plus checked_at (YouTube: when the channel was last re-read), channel_created_at, long_video_count, shorts_count, last_short_at (YouTube) and following, markets (Instagram). CONTACTS, BIOS, VIDEOS AND POSTS ARE NEVER RETURNED — has_email is only a yes/no. Free accounts can open a limited number of cards per day. QUOTA: 1 MCP credit (one entity card). 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.

Input Schema

Name	Required	Description	Default
`slug`	Yes	the creator slug as returned by search_influencers
`platform`	Yes	youtube or instagram

Output Schema

Name	Required	Description
`url`	No
`name`	No
`slug`	No
`error`	No	Present only when isError is true: machine-readable failure. The human explanation stays in content.
`niche`	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.
`country`	No
`markets`	No
`category`	No
`platform`	No
`username`	No
`avg_views`	No
`followers`	No
`following`	No
`has_email`	No
`lang_hint`	No
`checked_at`	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.
`count_views`	No
`is_verified`	No
`media_count`	No
`last_post_at`	No
`shorts_count`	No
`stats_hidden`	No
`last_short_at`	No
`last_video_at`	No
`long_video_count`	No
`channel_created_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026

addedOutput schema / properties / addon_hints

Added value: +{
+  "description": "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.",
+  "items": {
+    "properties": {
+      "available_data_types": {
+        "description": "kinds of data the module confirmedly has for the object",
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "info_url": {
+        "description": "the object (or its limited breakdown) inside the module on spytrend.com",
+        "type": "string"
+      },
+      "module": {
+        "description": "nutra | crypto | web2app | search_arb | startups",
+        "type": "string"
+      },
+      "object_id": {
+        "description": "the ad id, or the site domain for site rows",
+        "type": "string"
+      },
+      "preland_downloadable": {
+        "description": "Nutra / Crypto: the saved pre-lander can be downloaded in the module",
+        "type": "boolean"
+      },
+      "subscription_status": {
+        "description": "active | not_connected",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

AddedOct 5, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnly/openWorld annotations, the description discloses negative behavior ('CONTACTS, BIOS, VIDEOS AND POSTS ARE NEVER RETURNED — has_email is only a yes/no'), per-platform field availability, daily free-tier limits, credit cost, and pricing escalation. These are behavioral facts nothing in the annotations or schema conveys.

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 core capability and field list are front-loaded, and the all-caps warnings about withheld data earn their emphasis. The QUOTA/PRICING block is verbose and partly instructional policy rather than tool semantics, but it remains dense and purposeful rather than filler.

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 two-param, read-only lookup with an output schema, the description covers cost, consent, rate limits, and the field-difference between platforms. The only mild redundancy is restating return fields that the output schema already defines, which does more good than harm for a paid tool.

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% and both parameters are enum/typed with their own descriptions, so the schema does the heavy lifting. The description reinforces that slug comes from search_influencers and that platform drives which return fields appear (YouTube-only vs Instagram-only), which is useful but marginal at the parameter level.

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 creator card from the influencer directory') and states the exact addressing scheme (platform + slug). It explicitly contrasts with search_influencers by saying the card has 'the same fields as a search row plus' extras, so an agent can distinguish it from the sibling search tool without opening either schema.

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 specifies the prerequisite ('slug as returned by search_influencers'), the access constraints ('Free accounts can open a limited number of cards per day'), and a concrete pre-call sequence: get max debit from estimate_cost (free), tell the user, then one-time consent via accept_pricing_terms. That is explicit when-to-use and how-to-prepare guidance referencing the correct siblings.

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.