Skip to main content
Glama

Get GIF

get_gif
Read-onlyIdempotent

Fetch complete details for one GIF by its search result ID, including direct URL, dimensions, license, and attribution for proper use.

Instructions

Fetch full details for one GIF by the id returned from search_gifs (e.g. "wikimedia:File:Foo.gif" or "openverse:").

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": {
      "id": "<id>"
    },
    "name": "get_gif"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesGIF id from search_gifs.
safetyNoContent filter. 'safe' (default) also removes violence/gore/drug terms; 'moderate' only removes sexual/explicit and hate content. There is no unfiltered mode.safe

Output Schema

NameRequiredDescriptionDefault
gifYes
foundYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, open-world profile, so the description is not required to restate safety. It adds genuinely new behavioral context by disclosing that ids are provider-prefixed (wikimedia:, openverse:) and that results are the detailed record rather than a search hit. It says nothing about the safety filter's effect on retrieval, which is the only remaining gap.

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?

One sentence, front-loaded with the action and resource, with the id provenance and format examples packed in as a parenthetical. Nothing is wasted and nothing essential is buried.

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?

An output schema exists and both parameters are fully described in the schema, so the description needn't explain return values or field semantics. What remains is minor: no mention of behavior when an id is stale or filtered out, which matters slightly for an open-world lookup tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes beyond the schema by giving concrete id format examples that the schema field text omits. The safety parameter is fully documented in the schema, so no compensation is needed there.

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?

Specific verb ('Fetch full details') plus resource ('one GIF'), with the scope explicitly narrowed to a single item versus the sibling search_gifs. The contrast between 'full details' and search results lets an agent distinguish the two tools without reading either schema.

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?

The description states the prerequisite clearly: the id must come from search_gifs, which tells the agent this is a follow-up call after a search. It does not name a when-not-to-use case or state what happens on a missing/invalid id, but the intended entry point is unambiguous.

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