Skip to main content
Glama
hanoak

pixabay-mcp-server

by hanoak

Get Pixabay Video

pixabay_get_video
Read-only

Fetch a Pixabay video by ID and receive all available size tiers. Use for accessing specific videos from search results.

Instructions

Fetch a single Pixabay video by id (e.g. one returned from pixabay_search_videos), including every size tier Pixabay provides for it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesThe Pixabay video id to retrieve, e.g. from a pixabay_search_videos result.
Behavior4/5

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

Annotations already declare read-only and open-world; the description adds that the response contains every size tier, providing useful behavioral context beyond what annotations offer.

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?

A single concise sentence that is front-loaded with the verb and resource, and adds relevant detail without unnecessary words.

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

Completeness5/5

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

For a simple one-parameter read-only tool with clear annotations and no output schema, the description gives enough context about the return value (all size tiers) and usage context.

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 is 100% covering the id parameter, and the description repeats the same information without adding new semantic meaning, warranting the baseline score.

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 the tool fetches a single video by ID, distinguishing it from search and image tools. It also specifies that all size tiers are included, making the scope precise.

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?

It clearly indicates when to use (when you have an ID from pixabay_search_videos), but doesn't explicitly state when not to use or name alternatives, though sibling tools imply them.

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/hanoak/pixabay-mcp-server'

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