Skip to main content
Glama

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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "platform": "<platform>",
      "slug": "<slug>"
    },
    "name": "get_influencer"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesthe creator slug as returned by search_influencers
platformYesyoutube or instagram

Output Schema

NameRequiredDescriptionDefault
urlNo
nameNo
slugNo
errorNoPresent only when isError is true: machine-readable failure. The human explanation stays in content.
nicheNo
paramsNoRequest 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.
countryNo
marketsNo
categoryNo
platformNo
usernameNo
avg_viewsNo
followersNo
followingNo
has_emailNo
lang_hintNo
checked_atNo
addon_hintsNoAdd-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_viewsNo
is_verifiedNo
media_countNo
admin_sourceNo
last_post_atNo
shorts_countNo
stats_hiddenNo
last_short_atNo
last_video_atNo
long_video_countNo
channel_created_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / admin_source
      Added value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  2. Changed1 schema field changed
    • 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"
      +}
  3. Added

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 it discloses quota cost (1 MCP credit), pricing tiers after 500 credits/month, one-time consent requirement, and free-account daily card limits. It also states a hard data boundary — contacts, bios, videos and posts are never returned and has_email is boolean only — which prevents wasted calls.

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?

Front-loaded with the core action, then fields, then exclusions, then cost. Dense but nearly every clause carries information; the all-caps exclusion and pricing tail slightly hurt readability but are not wasteful.

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?

An output schema exists, and the description still summarizes what fields to expect and which are platform-specific, plus cost and consent prerequisites. For a paid, quota'd single-entity lookup, nothing an agent needs before calling is missing.

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?

Schema coverage is 100%, so baseline is 3, but the description adds meaning: it explains that slug comes from search_influencers and that platform choice changes which fields are present (YouTube-only vs Instagram-only fields). It does not add format or validation detail for the values themselves.

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 verb and resource ('Fetch one creator card from the influencer directory') and immediately names the two keying dimensions (platform, slug). It also distinguishes itself from the sibling search_influencers by framing the slug as what that tool returns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells the agent to obtain slug from search_influencers and to call estimate_cost and accept_pricing_terms before invoking, which is real routing guidance. It stops short of stating when NOT to fetch a card (e.g., bulk lookups should use search_influencers instead), so it is not fully exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.