Skip to main content
Glama

Tenor

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Posts

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYes
client_keyNo
media_filterNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultsNoPosts by ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "ids": "12345678,87654321"
+  },
+  {
+    "ids": "16017442",
+    "media_filter": "gif"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "results": {
+      "description": "Posts by ID",
+      "items": {
+        "properties": {
+          "content_description": {
+            "description": "Content description",
+            "type": "string"
+          },
+          "created": {
+            "description": "Creation timestamp",
+            "type": "number"
+          },
+          "hasaudio": {
+            "description": "Has audio",
+            "type": "boolean"
+          },
+          "id": {
+            "description": "Post ID",
+            "type": "string"
+          },
+          "itemurl": {
+            "description": "Item URL",
+            "type": "string"
+          },
+          "media_formats": {
+            "description": "Media formats",
+            "type": "object"
+          },
+          "shares": {
+            "description": "Share count",
+            "type": "integer"
+          },
+          "tags": {
+            "description": "Associated tags",
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "title": {
+            "description": "Title",
+            "type": "string"
+          },
+          "url": {
+            "description": "Post URL",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive nature. The description adds behavioral context by specifying the comma-separated IDs format and the return purpose (re-resolving media URLs and metadata). It does not introduce contradictions or undisclosed destructive behaviors, and the added context is valuable beyond annotations.

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?

The description is a single, well-structured sentence that front-loads the primary action. It is concise with no redundant wording, and every piece of information (resource, scope, use case) contributes to understanding.

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?

The tool has a simple 3-parameter schema, a comprehensive annotation set (read-only, idempotent, non-destructive), and an output schema. The description covers the main purpose and usage context, and it adds the comma-separated detail. It does not need to explain return values due to output schema; the only minor gap is no mention of optional parameters, but their names are self-explanatory.

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 0%, so the description must compensate. It provides the comma-separated format for the 'ids' parameter, which is not in the schema. However, it does not explain 'client_key' or 'media_filter', leaving these parameters without additional semantics. Partial compensation, hence a 3.

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?

The description uses a specific verb 'Fetch' and clearly states the target resource (Tenor GIFs/stickers) and scope (by post IDs). It explicitly distinguishes from sibling tools like search and featured by noting it re-resolves results from those tools, indicating a unique purpose.

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?

It explicitly states when to use the tool: 're-resolve media URLs and metadata for results returned earlier by search or featured.' This gives clear context for usage, though it does not explicitly list when-not-to-use or alternative tools; however, the mention of search/featured as the source of IDs implies this is not for discovery.

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

All Tenor toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources