Skip to main content
Glama

GMPSignal Real-Time Intelligence MCP (59 Tools)

tiktok_profile_video_all_in_one

Read-onlyIdempotent

TikTok Video & Profile Scraper All-in-One (Flat Rate): Real-time structured data extraction feed for TikTok Video & Profile Scraper All-in-One (Flat Rate).

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": "tiktok_profile_video_all_in_one"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxResultsNoMaximum number of records to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / maxResults / description
      Previous value: -"Maximum number of structured items to extract."New value: +"Maximum number of records to return."
  2. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -true
  3. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +true
  4. Added

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered without the description. The only behavioral addition is "Real-time," which does not explain return payload shape, rate limits, pagination, or what the "Flat Rate" billing implication means for the caller. No contradiction with annotations exists.

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

Conciseness2/5

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

It is short, but length is not the issue: the single sentence is circular, spending half its words re-quoting the full product name as the definition of that same product name. No actionable information is front-loaded, so the compactness is under-specification rather than efficiency.

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

Completeness2/5

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

For a scraping tool with no output schema, the description should say what fields come back and what input identifies the target, yet it does neither. The schema has zero required parameters, which makes the missing explanation of how the scraper knows which TikTok profile or video to fetch a serious completeness 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?

With one parameter and 100% schema description coverage, the schema already explains maxResults as the record cap, so the baseline of 3 applies. The description adds no meaning beyond that and notably never explains the more important question of how the target profile or video is identified given that no parameters are required.

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

Purpose2/5

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

The description is essentially a tautology: "TikTok Video & Profile Scraper All-in-One (Flat Rate): Real-time structured data extraction feed for TikTok Video & Profile Scraper All-in-One (Flat Rate)" restates the tool name twice. Only the fragment "Real-time structured data extraction feed" hints at an actual verb+resource (scraping TikTok video and profile data), and it offers no differentiation from the sibling scrapers like instagram_profile_posts_all_in_one or youtube_video_transcript_channel_scraper.

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 when-to-use guidance, no prerequisites, and no mention of alternatives among the many sibling scraper tools. An agent would be guessing whether this tool targets a profile, a single video, or a feed, since nothing in the text or parameters clarifies the scope.

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