Skip to main content
Glama

List trending AI meme video templates

list_trending_memes
Read-onlyIdempotent

List trending TikTok AI meme video templates on PugSoda, ordered by heat and recency, with subject requirements (1 person, 2 people, couple, or pet), clip length, starting one-time price, free preview availability, and direct upload URL.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_trending_memes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of templates to return (1–50, default 15).
subjectNoOptional filter by who goes into the video: person (1 person), pair (2 people), couple, or pet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds real value by enumerating the payload fields each template carries (subject requirements, clip length, starting one-time price, free preview, upload URL). It omits pagination behavior and whether 'heat' ordering can be changed.

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 dense sentence with no filler, and the resource plus ordering lead the sentence. The long mid-sentence list of returned fields makes it slightly harder to scan than a short sentence followed by a return-value clause would be.

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?

With no output schema, the description does the necessary work of listing what each result contains, which is the main gap that would otherwise exist. For a simple two-parameter read-only listing with full annotation coverage, only pagination/ordering-control details are missing.

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 coverage is 100% and both parameters are fully described in the schema, so the baseline is 3. The description restates the subject categories (person, pair, couple, pet) already present in the enum descriptions and says nothing about the limit parameter or defaults.

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 ('List trending TikTok AI meme video templates on PugSoda') plus the ordering ('heat and recency') and the fields returned. It is specific enough to be actionable, but never contrasts itself with search_templates, so an agent must infer the boundary between browsing trending and searching.

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?

'Trending' implies a default discovery/browse use case, and the optional subject filter hints at narrowing, but there is no explicit statement of when to use this versus search_templates or get_template. No prerequisites or exclusions are given.

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.