Skip to main content
Glama

Search PugSoda video and photo studio templates

search_templates
Read-onlyIdempotent

Search all PugSoda AI video templates, TikTok meme swaps, themed family photo studios, and product video templates by keyword, theme, or subject.

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
limitNoMaximum number of templates to return (1–50, default 20).
queryNoKeyword to match against template title, H1, teaser, description, or tags (e.g. "cat", "car", "dance", "saloon", "christmas").
themeNoOptional theme or tag filter (e.g. "halloween", "pets", "cars", "dance", "songs").
subjectNoOptional filter by subject type.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is fully covered. The description adds nothing behavioral beyond that: no relevance/ranking semantics, no empty-query behavior, no statement about result ordering. It is purely a restatement of scope.

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 no filler sentences or hedging. The enumerated template categories (TikTok meme swaps, family photo studios, product videos) are slightly promotional but do convey content breadth efficiently.

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?

For a simple four-optional-parameter search with no output schema and complete annotation coverage, the description is adequate but incomplete: it does not state what happens with zero filters, how results are ordered, or how query and theme combine. These are the only gaps an agent would need filled to call it confidently.

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 100% with examples and enum values supplied for query, theme, subject, and limit, so the schema carries parameter meaning. The description adds only the high-level idea of searching by keyword/theme/subject and does not clarify interactions between query and theme or default behavior when parameters are omitted. Baseline 3 applies.

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?

A specific verb (search) plus resource (PugSoda AI video/photo templates) with the matchable dimensions named: keyword, theme, subject. It covers the content categories well enough that an agent can distinguish it from the singular get_template lookup, though it never explicitly contrasts the two.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description only restates the three filter axes already exposed by the schema. It gives no guidance on when to prefer this over get_template or list_trending_memes, no mention of what an empty query returns, and no indication of result ordering or relevance behavior.

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.