Skip to main content
Glama

Giphy

by io.github.pipeworx-io
OverviewAdmin

Trending Gifs

trending_gifs
Read-onlyIdempotent

Get currently trending GIFs on Giphy. Returns title, URL, rating, and multiple image sizes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of results to return (1–25, default 10)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
gifsYesArray of trending GIF objects
countYesNumber of trending GIFs returned

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 trending GIFs returned",
+      "type": "number"
+    },
+    "gifs": {
+      "description": "Array of trending 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"
+    }
+  },
+  "required": [
+    "count",
+    "gifs"
+  ],
+  "type": "object"
+}
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "limit": 10
+  }
+]
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior, so the description does not need to repeat safety traits. It adds value by specifying the return contents (title, URL, rating, multiple image sizes), which sets expectations beyond the schema. No contradictions found.

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 a single, direct sentence that begins with the action verb and clearly states the resource and return contents. It has no filler or redundant information, making it extremely concise and well-structured.

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 read-only tool with one optional parameter, strong annotations, and an output schema, the description is fully adequate. It explains what the tool does and what is returned, leaving no critical gaps for an agent to invoke it correctly.

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?

Input schema covers 100% of the one parameter (limit) with clear range and default, so the description does not need to add parameter details. The mention of 'multiple image sizes' pertains to output rather than parameters, and the description does not enhance parameter understanding beyond the schema.

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 it retrieves currently trending GIFs from Giphy, using a specific verb and resource. It distinguishes itself from sibling tools like search_gifs and random_gif by focusing on the 'currently trending' scope, making the purpose unambiguous.

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 trending GIFs but does not explicitly mention alternatives or when-not-to-use. Sibling tools like search_gifs and random_gif are not referenced, so guidance is only implied through the phrase 'currently trending'.

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