Skip to main content
Glama
farukkolip

TikTapDown MCP

generate_tiktok_hook

Generate three proven viral TikTok hook templates for your chosen category, complete with examples and tips to boost engagement.

Instructions

Generate proven viral TikTok hook formulas for a specific category. Returns 3 ready-to-use hook templates with examples and tips.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNoOptional: your specific topic to customize examples (e.g. 'fitness', 'investing', 'cooking')
categoryYesThe hook category/type that fits your content
Behavior3/5

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

No annotations provided, so description carries burden. States it 'returns' templates (read behavior). Does not disclose authentication needs, rate limits, or what happens with invalid input (though enum prevents invalid category). Adequate for a generation tool, but could note that it is a safe, stateless operation.

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 sentence, no extra words. Key info (purpose, category constraint, output quantity) is front-loaded. Every element earns its place.

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 two parameters (one optional, one enum) and no output schema, the description sufficiently covers what is needed. It states return format (3 templates with examples and tips). Minor gap: no detail on whether 'topic' modifies examples, but schema description covers it. Slightly above baseline.

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% with descriptions for both parameters. Description adds no additional semantics beyond the schema's own descriptions of 'category' and 'topic'. 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?

Description uses specific verb 'generate' and resource 'viral TikTok hook formulas' with clear scope: 'for a specific category'. It specifies output quantity (3 templates). Distinct from all sibling tools which deal with analytics, formatting, or downloads.

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?

Implied usage context for content creation, but no when-not or alternative tool guidance. Since siblings are unrelated, the tool is self-contained, but explicit usage instructions are missing.

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