Skip to main content
Glama
farukkolip

TikTapDown MCP

get_tiktok_keyword_research

Discover TikTok keyword search intent, related keywords, and content angle ideas for planning your content strategy.

Instructions

Get TikTok-specific keyword research data: search intent type, suggested related keywords, and content angle ideas. Useful for planning a TikTok content calendar.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordYesSeed keyword to research (e.g. 'meal prep', 'productivity hacks', 'iPhone tips')
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only states the output types but does not mention side effects, rate limits, authentication needs, or whether it is a read-only operation. For a tool that likely performs a read query, more transparency is needed.

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?

The description is two sentences long, with the first sentence stating the purpose and outputs, and the second providing a use case. Every part is useful and no unnecessary words.

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?

Given no output schema, the description sufficiently explains the types of data returned (search intent, related keywords, content angle ideas). For a research tool with a single parameter, this is adequate, though an indication of return format or pagination would improve completeness.

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?

With 100% schema description coverage, the input schema already explains the 'keyword' parameter with examples. The tool description does not add additional semantic context beyond what the schema provides, so a baseline score of 3 is appropriate.

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 clearly states the verb 'Get' and the resource 'TikTok-specific keyword research data' and lists specific outputs: search intent type, suggested related keywords, and content angle ideas. It distinguishes well from sibling tools which cover engagement rate, RPM, hashtags, etc.

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?

The description offers a concrete use case ('planning a TikTok content calendar'), which helps the agent decide when to use this tool. However, it does not explicitly mention when not to use or compare with alternatives; though siblings are clearly different, so the context is strong.

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/farukkolip/tiktapdown-mcp'

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