Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bing_videos

Search Bing video results for any query. Returns structured JSON with pagination, locale, and country options via Crawlora MCP.

Instructions

Search Bing video results. Returns Bing video search results for a query string. Locale defaults to country=us and lang=en-us. Returns 503 when Bing serves a challenge page or unusable results.

Input Schema

NameRequiredDescriptionDefault
qYesSearch query
langNoBing UI language; defaults to en-us
pageNo1-based page number; defaults to 1
countNoResults per page; defaults to 10, clamped to 1..50
countryNoTwo-letter country code; defaults to us

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.6.0
  2. Removedv1.6.0
  3. First observedv1.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It usefully discloses the default locale and, notably, that a 503 is returned when Bing serves a challenge page or unusable results. It does not mention auth, rate limits, or result/pagination behavior.

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?

Three short sentences, front-loaded with the core action before the locale and error details. No filler; only the redundant restatement of defaults costs it.

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?

Covers purpose, defaults, and one failure mode, but with no output schema and no annotations a five-parameter search tool would benefit from noting pagination semantics or result shape. Adequate but with visible gaps.

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 five parameters are already documented with types and defaults in the schema. The description's locale note largely restates the schema defaults rather than adding syntax or constraints, so baseline 3 is appropriate.

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?

States a specific verb and resource (search Bing video results) and the 'video' qualifier distinguishes it from bing_search, bing_images, and bing_news. It does not explicitly name a sibling, but the medium is unambiguous.

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?

No when-to-use guidance and no alternatives named (e.g., brave_videos, google_videos, yahoo_search_videos). Usage is only implied by the word 'Search'.

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