Skip to main content
Glama

google_shorts

Retrieve Google Shorts search results including thumbnails, GIF previews, account names, and publication dates. Supports pagination via offset.

Instructions

Retrieves Google Shorts (short video) search results with thumbnails, GIF previews, account names, and publication dates. [Credits: Not specified in documentation] Notes: Pagination is offset-based via start, unlike most other endpoints in this category which use page. Returns: { short_videos_results: [{title, source, thumbnail, gif_url, account_name, date}] }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
lrNoLimit search to one or multiple languages, formatted lang_{language code}.
tbsNoAdvanced parameter ('to be searched') to filter search results.
htmlNoReturn the full HTML of the Google page. (default: false)
nfprNoSet 1 to exclude auto-corrected/misspelled-query results, 0 to include them. (default: 0)
safeNoAdult content filter. Allowed values: active, off. (default: off)
uuleNoEncoded geographic location/locale to tailor results, e.g. w+CAIQIFJlbGF5IFN0YXRlcw==.
queryYesGoogle query. Example: query=shoes
startNoNumber of results to skip for pagination, e.g. start=12 skips the first 12 results.
domainNoGoogle domain for local results, e.g. google.co.in for India, google.co.uk for the UK. (default: google.com)
countryNoTwo-letter country code for the Google search (e.g. US, UK, FR). (default: us)
languageNoLanguage of the results, e.g. en, es, fr, de. (default: en)
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses the return format and pagination uniqueness, but does not mention whether the tool is read-only, requires authentication, or handles errors. This is adequate but not fully transparent for a search tool.

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?

The description is a single, focused paragraph with the purpose upfront, followed by a critical pagination note and a clear return structure. No unnecessary words, earning 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?

The description provides a return structure example, compensating for the missing output schema. It covers the essential behavioral note on pagination. However, it lacks explicit mention of idempotency or error scenarios, which are minor gaps for a simple search tool.

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 all 11 parameters described, so the description adds no additional semantic value beyond the schema. The mention of pagination offset is a behavioral note, not parameter-specific. Baseline 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?

The description clearly states it retrieves Google Shorts search results, specifying the type of content (short videos) and listing returned fields (thumbnails, GIF previews, account names, dates). This distinguishes it from siblings like google_videos or google_search which cover general video or web search.

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 explicitly notes that pagination uses offset-based 'start' unlike other endpoints using 'page', providing clear context for correct usage. However, it does not explicitly state when to use this tool versus alternatives, though the purpose is self-explanatory for short video queries.

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/alessandrobenigni/ScrapingDog-MCP'

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