Skip to main content
Glama

Search videos

search_videos
Read-onlyIdempotent

Search stock videos; returns real video URLs. Needs an active project.

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": {
      "query": "<query>"
    },
    "name": "search_videos"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
project_idNoProject id (or use session from use_project)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered. The description adds two useful behavioral facts: there is a project prerequisite and results contain real (usable) video URLs. It does not cover what happens without a project, licensing, pagination or result counts.

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?

Two short clauses, prerequisite and output nature front-loaded before any detail, with no filler. It is on the terse edge rather than wasteful, which is the right failure mode for a small tool.

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 2-parameter read-only tool with no output schema, the description covers the precondition and the returned content type, which is close to sufficient. The main remaining gap is what a 'query' should contain and what the result set looks like (count, paging).

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 50%: project_id is documented in the schema with the 'or use session from use_project' hint, while query has no description anywhere. 'Needs an active project' partly compensates by explaining the project_id precondition, but query syntax and semantics are left entirely undefined.

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 specific verb and resource ('Search stock videos') and, by naming the media type, implicitly separates it from siblings like search_photos, search_icons and search_files. It stops short of any explicit sibling routing, so it lands at a clear-but-undifferentiated 4.

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

Usage Guidelines3/5

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

'Needs an active project' states a precondition that tells the agent when this tool is usable and hints at the session setup path. It offers no explicit when-not guidance and names no alternative tool for the case where no project is active or where photos/icons are wanted.

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