Skip to main content
Glama

Search Bar Typing Animation Maker

create_search_bar_typing_animation
Read-onlyIdempotent

Prefill the Search Bar Typing Animation Maker: a search bar animation: a query typed letter by letter, then the search button pressed. Returns a link that opens the Tool with these options; the user presses Export there to download the video. All options are optional. Icons and images that need a file upload are not supported.

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

Input Schema

NameRequiredDescriptionDefault
qNoThe search query that gets typed. Default: "how to make a video intro".
bgNoBackground color. Default: "#00ff00".
cpsNoTyping speed in characters per second. Default: 8.
fpsNoExport frame rate. Default: "30".
resNoExport resolution. Default: "720".
fontNoFont id of the text. Default: "inter".
holdNoSeconds the final frame holds at the end. Default: 1.
leadNoSeconds of empty search bar before typing starts. Default: 1.
lookNoLight or dark search bar style. Default: "light".
sizeNoVideo size (aspect ratio) preset. Default: "16:9".
textNoColor of the typed text. Default: "#202124".
pauseNoSeconds between finishing typing and pressing the button. Default: 0.5.
pressNoWhether the search button is pressed after typing: 1 yes, 0 no. Default: true.
scaleNoSize of the search bar relative to the frame. Default: 100.
accentNoAccent color of the search button. Default: "#2563eb".

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 cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely non-obvious behavior: the return value is a link to an editor where export must be triggered manually, and icon/image uploads are unsupported. It does not discuss link lifetime or export timing, so it is not fully exhaustive.

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?

Short and front-loaded, with the key workflow fact (returns a link; export happens elsewhere) early. Minor waste from restating the title verbatim and an awkward double-colon construction, but no filler sentences.

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 15-parameter, zero-required, fully documented prefill tool with no output schema, the description supplies the essential missing piece: what the call returns and what the user must do next, plus the upload limitation. Only secondary details such as link validity or whether settings can be changed later are absent.

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%, so the schema already documents all 15 parameters with defaults, ranges, and enums. The description only adds the high-level narrative that the query is typed letter by letter and the button may be pressed, which mildly reinforces 'q' and 'press' but adds no new semantics for the remaining options.

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?

Uses a specific verb ('Prefill') plus a named resource and describes the resulting animation ('a query typed letter by letter, then the search button pressed'), which separates it from the chart-race/counter/countdown siblings. It stops short of explicitly contrasting itself with any alternative, but the resource is unambiguous.

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?

Conveys the workflow (call to get a link, then the user presses Export in the Tool to download) and notes that all options are optional, so defaults are implied. It does not state when to choose this animation over the sibling animation makers, and the only exclusion is the file-upload limitation.

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.