Skip to main content
Glama

Tenor Search

tenor_search
Read-onlyIdempotent

Search Tenor's GIF and sticker library by keyword (q); supports locale, content-safety filter, aspect-ratio range, randomization, and pagination; returns media URLs and metadata.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "cat dancing"
    },
    "name": "tenor_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYes
posNo
limitNo
localeNo
randomNo
ar_rangeNo
client_keyNo
media_filterNo
contentfilterNooff|low|medium|high

Output Schema

NameRequiredDescriptionDefault
nextNoPagination token for next results
resultsNoSearch results

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already establish this as a read-only, open-world, idempotent, non-destructive call, so the safety profile is covered. The description adds that results include media URLs and metadata and that content-safety and locale options exist, but it omits behavioral context such as rate limits, whether client_key is a credential the caller must supply, or how pagination behaves.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence packs the verb, resource, required parameter, and option list with no filler. Density is high but structure is clean; the only cost is that the parenthetical (q) plus long option list reads as a feature dump rather than prioritized guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Because an output schema exists, the description need not explain return values, and its brief note about media URLs and metadata is sufficient. For a 9-parameter open-world search tool, though, leaving two parameters undocumented and offering no alternative-tool routing makes it only minimally complete.

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 only 11% across 9 parameters, so the description must carry weight, and it does partially: locale, contentfilter, ar_range, random, and pagination map to named options. However, media_filter and client_key get no explanation at all, and 'pagination' is left vague as to which parameter controls it.

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 Tenor's GIF and sticker library by keyword') and pins the required parameter q to that action, so an agent knows exactly what the tool does. It does not distinguish itself from GIF-related siblings such as tenor_autocomplete, tenor_categories, or tenor_featured, so the differentiation component is missing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance: nothing says to prefer this over tenor_autocomplete for partial queries or over tenor_categories/tenor_featured for browsing. The only implicit signal is that keyword search requires q, which is a weak substitute for real routing guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.