Skip to main content
Glama

Tenor Featured

tenor_featured
Read-onlyIdempotent

Fetch Tenor's current editorially featured GIFs; supports locale, content filter, aspect-ratio range, 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": {
      "limit": 20
    },
    "name": "tenor_featured"
  }
}

Input Schema

NameRequiredDescriptionDefault
posNo
limitNo
localeNo
ar_rangeNo
media_filterNo
contentfilterNo

Output Schema

NameRequiredDescriptionDefault
nextNoPagination token for next results
resultsNoFeatured GIFs

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?

Annotations already declare readOnly, openWorld, idempotent, and non-destructive, so the safety profile is covered. The description adds that results are curated and filterable, but says nothing about rate limits, authentication, pagination cursor behavior, or default page size, and its mention of return values is redundant given an output schema exists.

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 that wastes no words, with the resource stated first and capabilities after. The semicolon clauses are dense but readable; only the redundant return-value clause could be cut.

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?

With an output schema present, omitting return-value detail is fine, and the annotations cover safety. However, six free-form parameters at 0% schema coverage with no enums means an agent cannot construct a valid filtered call (ar_range syntax, contentfilter levels, cursor format) from this definition alone.

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 parameter meaning, yet it only gestures at four of six parameters by name-concept (locale, content filter, aspect-ratio range, pagination). It gives no accepted values for contentfilter or media_filter, no format for ar_range, no default or maximum for limit, and never explains pos as a cursor.

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?

States a specific verb and resource: "Fetch Tenor's current editorially featured GIFs." The word "editorially featured" distinguishes it in spirit from a query-driven search sibling, but no sibling is named, so the differentiation is only implicit.

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 description implies the use case (browse curated content rather than search by query) but never says when to pick this over tenor_search or tenor_categories, and gives no prerequisites or exclusions. Usage is inferable rather than stated.

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.