Skip to main content
Glama
CreatorDB

creatordb-mcp-server

Official
by CreatorDB

get_tiktok_contact

Retrieve a TikTok creator's publicly listed email addresses by providing their handle. Designed for outreach and sponsorship discovery.

Instructions

Get a TikTok creator's contact email addresses (public-listed). Costs 15 credits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uniqueIdYesTikTok handle (e.g. "charlidamelio"). No "@" prefix and no URL.
Behavior3/5

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

Discloses cost (15 credits) but lacks other behavioral traits such as authentication requirements, rate limits, or error responses. No annotations exist, so description carries the full burden but does not fully cover.

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?

Single, focused sentence with no unnecessary text. Efficiently conveys purpose, data scope, and cost.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Provides essential information for a low-complexity tool: what it does, input format, and cost. Could mention return structure (e.g., an array of emails) but not critical for basic selection.

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% with one parameter. Description adds value by specifying format (no '@' prefix, no URL) beyond the schema's example. Provides concrete usage guidance.

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?

Clearly states the verb 'Get' and the resource 'a TikTok creator's contact email addresses (public-listed)'. Distinguishes from sibling tools like get_instagram_contact by specifying platform and data type.

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

Usage Guidelines3/5

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

No explicit guidance on when to use vs alternatives. The description implies usage for TikTok contact retrieval, but does not mention when not to use or compare with other TikTok tools like get_tiktok_profile.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CreatorDB/creatordb-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server