Skip to main content
Glama

Search meme video templates

search_templates
Read-only

Search TrendTemplate's AI trend video templates by meme name, alias or keyword. Each result has the creation page link, how many photos to upload, lengths and credit prices. Leave query empty to list the newest templates.

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": "search_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoMeme name or keyword, e.g. "wassup in a minute" or "car".
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real value beyond that by enumerating what each result contains (creation page link, photo count, lengths, credit prices) and by defining the empty-query behavior, which matters because there is no output schema.

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?

Three sentences, each carrying distinct information: what is searched, what comes back, and the empty-query fallback. The purpose is front-loaded and there is no filler or repetition of the title.

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?

For a read-only search with three optional parameters and no output schema, the description covers purpose, matching keys, result shape, and the empty-query case. The only gap is pagination behavior for limit and offset, which is left to the schema's defaults and bounds.

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 only 33%, with just the query parameter documented in the schema. The description reinforces query semantics (meme name, alias, keyword, empty = newest) but says nothing about limit or offset, so an agent must infer conventional pagination from names, defaults, and bounds alone.

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 gives a specific verb and resource ("Search ... AI trend video templates") and states the matching keys (meme name, alias, keyword). It is clearly distinguishable from the sibling get_template, which by name implies single-item retrieval, but it never names that sibling to draw the contrast explicitly.

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 provides a concrete usage rule for the empty-query case ("Leave query empty to list the newest templates"), which tells an agent exactly how to browse rather than search. It stops short of naming alternatives such as get_template or get_pricing, so no exclusions are 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.

Resources