Skip to main content
Glama

Press5 launch pad

Starter templates

list_templates
Read-only

List the free starter templates (café, portfolio, product landing page, link in bio, wedding, tradesperson, CV, coming soon, blog), each with a live preview_url and the fields that can be filled in. No account needed. Deploy one with deploy_site { template, fields }, or call get_template to fetch its files and change them first.

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_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

readOnlyHint=true already declares the safety profile, and the description adds context the annotation does not: the templates are free, no authentication is required, and each result carries a live preview_url plus its fillable fields. It does not discuss result ordering or size, but for a fixed-size catalog that is a minor gap.

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?

Two sentences, front-loaded with the action and return contents, followed by the next-step routing. The parenthetical template list is long but each item earns its place by letting the agent pick a template without an extra call.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, read-only listing with no output schema, the description covers what is in the results, the absence of auth requirements, and both plausible follow-up actions. Nothing an agent needs in order to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so the schema baseline is 4. The description compensates usefully by describing what each returned item contains (preview_url, fields), which partially substitutes for the missing output schema.

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?

Names a specific verb and resource ("List the free starter templates") and then enumerates the nine template types, so an agent knows exactly what comes back. It is clearly distinguishable from siblings like list_sites or get_template by signalling this is the catalog of starting points.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use deploy_site { template, fields } to ship one directly, or get_template to fetch and edit the files first. It also states the precondition "No account needed", which removes an otherwise likely gating question.

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