Skip to main content
Glama

Get this week's TikTok AI trends

get_trend_tracker
Read-only

Get the latest weekly ranking of TikTok trends that people are remaking with AI: distinct accounts posting AI versions in 24 hours, AI share, sound growth, stage, and whether a template exists. Data is CC BY 4.0; cite the page URL.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_trend_tracker"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoIssue date YYYY-MM-DD; omit for the latest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely non-structured behavior: the data is CC BY 4.0 and the page URL must be cited, which is an obligation an agent would otherwise miss. It stops short of stating refresh cadence guarantees or payload size, but the licensing obligation is the key addition.

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?

Two tight sentences: the capability and its metrics come first, the licensing/attribution note second. Nothing is repeated from the schema or annotations and no sentence is filler.

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?

For a single optional-parameter read tool with no output schema, the description effectively explains what comes back by listing the ranking fields, and it covers attribution. Missing only edge details such as behavior when a requested issue date does not exist, which is a minor gap.

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 description coverage is 100% and the single 'date' parameter is already documented as 'Issue date YYYY-MM-DD; omit for the latest.' The description adds no further meaning about date range limits, timezone, or how historical issues differ from the latest, so the baseline 3 applies.

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 names a specific verb and resource ('Get the latest weekly ranking of TikTok trends that people are remaking with AI') and enumerates the ranking dimensions returned (distinct accounts, AI share, sound growth, stage, template existence). That level of specificity clearly separates it from the pricing and template-lookup siblings.

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?

Usage is implied by the weekly/issues framing and 'omit for the latest', but there is no explicit when-to-use or when-not-to-use guidance, and no routing advice toward or away from the sibling tools such as get_template or search_templates. An agent can infer it is a read of ranking data, but must decide scope on its own.

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.

Resources