Skip to main content
Glama

Tenor Posts

tenor_posts
Read-onlyIdempotent

Fetch specific Tenor GIFs/stickers by their post IDs (ids, comma-separated), use to re-resolve media URLs and metadata for results returned earlier by search or featured.

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": {
      "ids": "12345678,87654321"
    },
    "name": "tenor_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes
client_keyNo
media_filterNo

Output Schema

NameRequiredDescriptionDefault
resultsNoPosts by ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so safety is covered. The description does add one genuinely non-obvious trait: that media URLs and metadata need to be re-resolved from stable post IDs, implying earlier URLs may be stale. It says nothing about the client_key requirement, rate limits, or batch-size constraints.

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 with the resource and ID-based scope stated before the usage hint. The parenthetical format note is compact and earns its place, though the sentence is dense enough that a break could improve scanability.

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. However, for a three-parameter lookup tool the definition leaves media_filter values and client_key purpose unaddressed, leaving the agent to infer them from examples 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 carries the burden of explaining three parameters. It clarifies only that ids is comma-separated and batchable; client_key and media_filter receive no explanation in either the description or the schema beyond a single example value.

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?

States a specific verb and resource (fetch Tenor GIFs/stickers by post IDs) and scopes it to ID-based lookup, which is clearly distinct from tenor_search and tenor_featured named in the same sentence.

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?

Explicitly frames the use case as re-resolving media URLs and metadata for results previously returned by search or featured, which tells the agent when to reach for this tool rather than re-running a search. It stops short of stating when not to use it (e.g., for fresh discovery), so it falls just short of the top band.

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.