Skip to main content
Glama

giphy_random

Read-onlyIdempotent

Fetch a random GIF from Giphy, optionally filtered by tag and content rating, for use in automated workflows or agent responses.

Instructions

Get a random GIF from Giphy, optionally by tag.

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": {
      "api_key": "<api_key>"
    },
    "name": "giphy_random"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoOptional tag to match
ratingNoContent rating cap
api_keyYesGiphy API key

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.11

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, non-destructive, open-world and idempotent behavior, so the description only needs to add context. It adds the 'random' selection behavior, but leaves out practical details such as result variability, rating filtering effects, or response shape; note also that 'random' sits in mild tension with idempotentHint=true, which the description does not address.

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 front-loaded sentence with zero filler. Everything stated is relevant and nothing needs trimming.

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?

For a simple three-parameter, read-only media lookup with full schema coverage and annotations covering the safety profile, this is nearly complete. The only gap is the absence of any hint about how it differs from giphy_search and giphy_trending in practice.

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%, so the schema already explains tag, rating, and api_key, making 3 the baseline. The description only echoes the tag parameter and says nothing about the rating cap or the required API key, so it adds little beyond the schema.

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 states a specific verb ('Get') and resource ('a random GIF from Giphy'), so the purpose is unambiguous. Compared with siblings giphy_search and giphy_trending, 'random' implicitly distinguishes it, though the description never names those siblings explicitly.

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 phrase 'optionally by tag' implies the two main usage modes (unfiltered random vs. tag-scoped random), which is useful. However, there is no guidance on when to choose this over giphy_search or giphy_trending, and no exclusions or prerequiory notes.

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