Skip to main content
Glama

Search GIFs

search_gifs
Read-onlyIdempotent

Find openly licensed animated GIFs by keyword and retrieve direct URLs, previews, dimensions, license, and attribution for compliant use.

Instructions

Search openly licensed animated GIFs by keywords (e.g. "cat", "rocket launch", "dancing"). Returns direct GIF URLs, preview URLs, dimensions, license and a ready-made attribution string. English keywords work best.

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_gifs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (1-25, default 8).
queryYesKeywords describing the GIF you want.
safetyNoContent filter. 'safe' (default) also removes violence/gore/drug terms; 'moderate' only removes sexual/explicit and hate content. There is no unfiltered mode.safe
sourceNo'auto' (default): Wikimedia Commons first, Openverse to fill gaps. Or force one source.auto
max_size_mbNoSkip GIFs whose file is larger than this many MB (default 10). Commons GIFs range from a few KB to 50+ MB.

Output Schema

NameRequiredDescriptionDefault
countYes
notesYes
queryYes
safetyYes
resultsYes
sourcesQueriedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so safety and side-effect behavior are covered structurally. The description adds genuinely useful context beyond that: the openly-licensed nature of results and the presence of a ready-made attribution string, which implies downstream attribution obligations the agent otherwise wouldn't know about. It stops short of describing result ranking or what an empty result looks like.

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 front-loaded sentences with no filler: purpose first, return shape second, a usage caveat last. The return-value enumeration is slightly gratuitous given an output schema exists, but it is short and reads naturally.

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?

With an output schema present and rich per-parameter schema descriptions, the remaining burden is small, and the description covers purpose, result contents, licensing and a usage hint. The one meaningful gap is the absence of any routing guidance relative to the sibling get_gif.

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% and every parameter (including enum meanings for safety and source, and the fallback semantics of "auto") is documented in the schema itself. The description contributes only the keyword-language hint for query, so the baseline 3 applies — the schema does the heavy lifting.

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 openly licensed animated GIFs") plus the input modality (keywords) and examples. It is distinguishable from the sibling get_gif by the word "search", but the description never explicitly contrasts the two, so it stops short of a 5.

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?

Usage context is implied — this is the discovery tool you use when you have keywords rather than an ID — but the description never says when to use it versus get_gif, nor does it state exclusions or prerequisites. The only concrete guidance is the linguistic hint that "English keywords work best."

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