Skip to main content
Glama
Sign In

Tokfluence

by com.tokfluence
OverviewDiscussionsAdmin

Get one creator

get_creator
Read-onlyIdempotent

Full cached record for a single creator: stats, contact details, topical hashtags, linked Instagram and YouTube, and the most recent posts we have stored.

Takes a tkc_* id or a bare TikTok username. Use it to check one creator in depth after search_creators has narrowed the pool; do not loop it over a whole page of search results, the search rows already carry what ranking needs.

The posts here come from cache, so they can be stale for a creator we have not scraped recently. When recency matters, use get_creator_posts.

Judge that staleness from newest_post_at, not last_analyzed_at. The second is when we read the profile and moves on every call; only the first says when the creator last posted. recency_note calls out a large gap between them.

The creator's profile picture and the covers of their recent posts are shown inline in the chat by default. Pass include_images: false if you only need the text.

Pass contacts: "none" for the profile without contact details: no email or phone values, and emails and phone numbers scrubbed from the bio and captions. has_email and has_phone still say whether we hold one. Same 1 credit.

Costs 1 credit.

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": {
      "creator": "<creator>"
    },
    "name": "get_creator"
  }
}

Input Schema

NameRequiredDescriptionDefault
creatorYesA tkc_* creator id or a TikTok username (with or without '@').
contactsNo"none" leaves out every email and phone number. Default "full".
include_imagesNoShow the profile picture and recent post covers inline in the chat. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover the safe-read profile (readOnly, idempotent, non-destructive); the description adds the substantive traits: data comes from cache and can be stale, the distinction between newest_post_at and last_analyzed_at, the existence of recency_note, inline image rendering by default, contact scrubbing behavior, and the 1-credit cost. This is real context an agent cannot get from the annotations.

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 summary, then usage routing, then caveats, then parameter notes, then cost. Every paragraph earns its place, though the newest_post_at vs last_analyzed_at explanation is somewhat long-winded and could be tightened without losing meaning.

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?

No output schema exists, and the description compensates by naming the key returned fields (newest_post_at, last_analyzed_at, recency_note, has_email, has_phone) and their interpretation. For a read-only single-record fetch, an agent has everything needed to call it and interpret results correctly.

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 the baseline is 3, but the description adds meaning the schema does not: what exactly contacts="none" scrubs (bio and captions, not just fields), that has_email/has_phone still indicate presence, that the credit cost is unchanged, and why you would set include_images=false. Only the creator id format is merely restated.

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 ('Full cached record for a single creator') and enumerates what the record contains: stats, contacts, hashtags, linked Instagram/YouTube, recent posts. It distinguishes itself from search_creators (narrowing) and get_creator_posts (recency) without the reader needing the schemas.

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?

Explicit when-to-use ('after search_creators has narrowed the pool'), explicit when-not ('do not loop it over a whole page of search results, the search rows already carry what ranking needs'), and names the alternative when recency matters ('use get_creator_posts'). Nothing is left to inference.

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

All Tokfluence toolsInspect
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.

Resources