Skip to main content
Glama
formfeed-dev

formfeed

Official
by formfeed-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List templates

list_templates
Read-only

List workspace templates, most recently changed first, to find the slug needed for schema validation and rendering. Returns id, slug, name, kind, engine, tags, and published version.

Instructions

Lists the templates of the workspace the API key belongs to, most recently changed first: id, slug, name, kind (pdf, image, docx for Word, pptx for PowerPoint), engine, tags and published_version. Call it first to find the slug that get_template_schema, validate_template and render take; skip it when the user already named the template. Returns every match in one answer, without archived templates, and an empty list when nothing matches. A template whose published_version is null has never been published, so render cannot use it yet. Read-only and free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoText to find in the name or slug, case-insensitive (e.g. invoice)
tagNoOnly templates with this tag; exact match, tags are lowercase with dashes (e.g. billing)
kindNoOnly templates that produce this kind of document
engineNoOnly templates written in this template language

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.3.10
    • addedInput schema / properties / engine / description
      Added value: +"Only templates written in this template language"
    • addedInput schema / properties / kind / description
      Added value: +"Only templates that produce this kind of document"
    • changedInput schema / properties / q / description
      Previous value: -"Search in name and slug"New value: +"Text to find in the name or slug, case-insensitive (e.g. invoice)"
    • addedInput schema / properties / tag / description
      Added value: +"Only templates with this tag; exact match, tags are lowercase with dashes (e.g. billing)"
  2. First observedv0.3.7

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark this as read-only and non-destructive, but the description adds meaningful behavior beyond that: ordering by most recent change, exclusion of archived templates, an empty list on no match, and the null published_version meaning render cannot use the template. The statement 'Read-only and free' reinforces the annotation without contradicting it.

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?

The description is dense but every sentence earns its place: it covers output fields, ordering, usage guidance, edge cases, and safety in a compact paragraph. Key guidance is front-loaded and no filler is present.

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?

With no output schema, the description sufficiently documents what the response contains, the available filter fields, the behavior with archived templates and empty results, and the special meaning of null published_version. It also provides enough context for an agent to decide when to call this tool versus its siblings.

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% and each parameter already has a clear description with examples and enum details. The tool description does not add significant parameter-level semantics beyond what the schema provides, so the baseline score of 3 is appropriate.

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?

The description states a specific verb and resource: 'Lists the templates of the workspace the API key belongs to', and specifies the returned fields and ordering. It also differentiates itself from sibling tools by explaining that it provides the slug used by get_template_schema, validate_template, and render.

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?

Explicit guidance is given: 'Call it first to find the slug... skip it when the user already named the template.' It also names the sibling tools that depend on this lookup and clarifies that archived templates are excluded and an empty list is returned when nothing matches.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools