Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

tiktok_search_hashtag

Search TikTok videos by hashtag to find posts tied to a topic, then use cursor pagination to collect more results.

Instructions

tiktok: Search by Hashtag. GET /v1/tiktok/search/hashtag. Search TikTok videos by hashtag. TikTok may return duplicate results. Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

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": {
      "hashtag": "<hashtag>"
    },
    "name": "tiktok_search_hashtag"
  }
}

Input Schema

NameRequiredDescriptionDefault
trimNoSet to true to get a trimmed response
cursorNoCursor to get more videos. Get 'cursor' from previous response.
regionNoAccepted for compatibility. The US feed is read.
hashtagYesHashtag to search for (without #)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it delivers real behavioral context: duplicate results are possible, success costs 1 credit, and errors, blocked, timed-out, invalid, and cached requests cost nothing. It still omits auth requirements, rate limits, and result ordering, which keeps it short of a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The endpoint and behavior are front-loaded, which is good, but the opening 'tiktok: Search by Hashtag' merely restates the following sentence, and the multi-clause billing sentence is dense and slow to parse. Part of it also defers to an external cost table rather than stating the fact.

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

Completeness3/5

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

For a four-parameter search tool with no annotations and no output schema, the description covers cost and result-quality caveats well. It does not describe the shape of returned videos or pagination behavior, both of which the agent must infer since no output schema exists to fill that 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 coverage is 100%, so all four parameters are already documented in the input schema. The description adds no further meaning about 'cursor', 'trim', or 'region' beyond what the schema states, which is the baseline 3 case.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a concrete verb and resource ('Search TikTok videos by hashtag') plus the underlying endpoint, so the agent knows exactly what the tool does. It does not distinguish itself from close siblings such as tiktok_search_keyword, which is the only thing keeping it from a 5.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives like keyword search. The purpose implies the usage context, but nothing in the text routes the agent between this and a sibling search tool.

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

Deploy Server

Other Tools