Skip to main content
Glama

Giphy

by io.github.pipeworx-io
OverviewAdmin

Search Gifs

search_gifs
Read-onlyIdempotent

Search Giphy for GIFs by keyword. Returns title, URL, rating, and multiple image sizes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results to return (1–25, default 10)
queryYesSearch query, e.g. "funny cats" or "celebration"

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
gifsYesArray of GIF objects
countYesNumber of GIFs returned in this response
totalYesTotal count of matching GIFs available

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of GIFs returned in this response",
+      "type": "number"
+    },
+    "gifs": {
+      "description": "Array of GIF objects",
+      "items": {
+        "properties": {
+          "downsized_url": {
+            "description": "Downsized GIF URL",
+            "type": "string"
+          },
+          "fixed_height_url": {
+            "description": "Fixed-height GIF URL",
+            "type": "string"
+          },
+          "gif_url": {
+            "description": "Original GIF URL",
+            "type": "string"
+          },
+          "height": {
+            "description": "Original GIF height in pixels",
+            "type": "number"
+          },
+          "id": {
+            "description": "GIF ID",
+            "type": "string"
+          },
+          "rating": {
+            "description": "Content rating (e.g., 'g', 'pg', 'pg-13', 'r')",
+            "type": "string"
+          },
+          "title": {
+            "description": "GIF title",
+            "type": "string"
+          },
+          "url": {
+            "description": "GIF page URL on Giphy",
+            "type": "string"
+          },
+          "width": {
+            "description": "Original GIF width in pixels",
+            "type": "number"
+          }
+        },
+        "required": [
+          "id",
+          "title",
+          "url",
+          "rating",
+          "gif_url",
+          "fixed_height_url",
+          "downsized_url",
+          "width",
+          "height"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total": {
+      "description": "Total count of matching GIFs available",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "count",
+    "gifs"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "funny cats"
+  },
+  {
+    "limit": 15,
+    "query": "celebration"
+  }
+]
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already cover read-only and non-destructive behavior. The description adds return content (title, URL, rating, multiple image sizes), providing useful context beyond annotations. No rate limits or other behavioral nuances are mentioned, but the added return info earns it a middle score.

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 two sentences long, front-loaded with the core action, and every word adds value. It is concise and well-structured without redundancy.

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 annotations declaring read-only/idempotent behavior, the description covers the essential purpose and return fields. It does not need to explain return structure in detail, so the description is adequately complete for this simple 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 description coverage is 100%, with both query and limit fully documented. The description does not add parameter-specific meaning beyond what the schema already provides, so it stays at the baseline of 3.

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 "Search Giphy for GIFs by keyword," specifying the verb (search), resource (Giphy), and method (by keyword). This distinguishes it from siblings like random_gif and trending_gifs, which serve different Giphy use cases.

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?

The description implies usage for keyword-based GIF searches but does not explicitly mention alternatives or exclusions. It lacks any reference to when to use this tool versus random_gif or trending_gifs, so guidance is only implied through the clear purpose.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Giphy toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources