Skip to main content
Glama

Trending Terms

trending_terms
Read-onlyIdempotent

Trending Tenor GIF and sticker keywords, the reaction, meme, emotion and pop-culture phrases people are currently typing into Tenor to find GIFs to send in chats and messaging apps. Returns Tenor's current trending GIF keyword list for a locale.

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": {
      "limit": 10
    },
    "name": "trending_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
localeNo

Output Schema

NameRequiredDescriptionDefault
resultsNoTrending search terms

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "limit": 10
      +  },
      +  {
      +    "limit": 5,
      +    "locale": "en_US"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "results": {
      +      "description": "Trending search terms",
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds only the useful nuance that results are 'current' (time-sensitive) and locale-scoped; it says nothing about refresh cadence, result size behavior, or what an empty locale yields.

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?

Two sentences, front-loaded with the concrete resource description. The second sentence largely restates the first in narrower form, which is mild redundancy but not damaging; nothing else is padding.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. However, with zero schema description coverage and a mutation-free but parameterized tool, the missing limit semantics and locale format leave real gaps an agent could stumble on.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry both parameters. It gestures at locale ('for a locale') without specifying the format, and it never mentions 'limit' at all — no default, range, or meaning — despite the schema's en_US and limit examples being the only hint.

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 resource — Tenor's current trending GIF/sticker keyword list — and characterizes the content as reaction, meme, emotion, and pop-culture phrases. That is far more informative than a restatement of the name, though the verb is only implied ("Returns") and no sibling is named for contrast.

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?

Usage is implied by "current trending... people are currently typing" — you would call it for fresh keyword inspiration — but the description never states when to prefer this over another source or any precondition. No exclusions or alternatives are offered, leaving the agent to infer the call context.

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.