Skip to main content
Glama
HasData

hasdata-mcp

Official

google_serp_short_videos: GET /

hasdata_google_serp_short_videos_getShortVideosSearchResults

Scrape Google Short Videos search results including TikTok, YouTube Shorts, and Instagram Reels. Returns video title, thumbnail, duration, source, creator, publish date, and direct URL for content discovery and trend monitoring.

Instructions

Get Short Videos Search Results

Scrapes the Google Short Videos carousel (TikTok, YouTube Shorts, Instagram Reels, etc.) for a query with location/uule, country (gl/cr), language (hl/lr), device type, and page-based pagination. Returns video title, thumbnail, duration, source platform, channel/creator, publish date, and direct video URL. Use for short-form content discovery, viral-trend monitoring, influencer research, cross-platform video aggregation, and sourcing short clips to summarize or embed in LLM responses.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query term for retrieving short videos results.
locationNoGoogle canonical location for the search.
uuleNoThe encoded location parameter.
glNoThe two-letter country code for the country you want to limit the search to.
lrNoThe 'lr' parameter specifies the language of the websites to return results from. This parameter filters results based on the language of the web content.
hlNoThe two-letter language code for the language you want to use for the search.
crNoThe country code for the country you want to limit the search to.
pageNoPage number for paginated results, where 0 is the first page.
deviceTypeNoSpecify the device type for the search.
Behavior3/5

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

With no annotations, the description carries the burden. It discloses the return fields (title, thumbnail, etc.) but does not mention rate limits, authentication, or side effects. It is adequate but not comprehensive.

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

Conciseness4/5

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

The description is two paragraphs and front-loaded with functionality, followed by use cases. It is concise but could be slightly tighter without losing meaning.

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?

Despite lacking an output schema, the description lists the return fields. It covers the main behavioral aspects for a scraping tool, though it could mention pagination limits or error handling.

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%, so the description adds minimal extra meaning. It groups parameters (location/uule, country, language) but does not significantly enhance the schema's own descriptions.

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 it scrapes the Google Short Videos carousel with query parameters. It distinguishes from sibling tools by specifying short videos, which is unique among the many Google SERP and platform-specific tools.

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 lists explicit use cases like short-form content discovery and influencer research, providing context for when to use the tool. However, it does not mention when not to use it or compare to alternatives.

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/HasData/hasdata-mcp'

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