Skip to main content
Glama
discord-mcp

discord-mcp

by zongwei-tang

search_gifs

Read-only

Find GIFs by keyword from Tenor or Giphy and return URLs to send as Discord message content.

Instructions

Search GIFs (Tenor/Giphy) like the GIF picker. Send the returned url as message content. [GET /gifs/search]

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": {
      "q": "<q>"
    },
    "name": "search_gifs"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesSearch text
limitNoMax results
localeNolocale
providerNotenor
media_formatNomp4 or gif

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, openWorld, non-destructive), so the description only needs to add context. It does: it discloses that results come from third-party providers, that the payload of interest is a URL, and that the URL should be forwarded as message content, plus the [GET /gifs/search] endpoint. It stops short of mentioning rate limits or result shape beyond the URL.

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?

Three short, front-loaded fragments: what it does, how to use the output, and the endpoint. Nothing is redundant and the actionable instruction (send the URL) is placed early.

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 no output schema, the description responsibly tells the agent the key return value is a URL and what to do with it, and the input schema is fully documented. Only a note on what to do when no results are returned is missing.

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 all five parameters are already documented and the baseline is 3. The only added meaning is naming Giphy alongside Tenor, which hints at valid provider values the schema's "tenor" default does not make obvious; no format or limit guidance is added.

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 names a specific verb and resource ("Search GIFs") and even names the underlying providers (Tenor/Giphy) plus the endpoint. It implicitly distinguishes itself from list_trending_gifs by framing this as query-driven search rather than a feed, but it never names that sibling 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 "like the GIF picker" and "Send the returned url as message content" imply the workflow (search, then post the URL), which is useful implied usage. There is no explicit when-to-use versus list_trending_gifs, and no stated exclusions or prerequisites.

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