Skip to main content
Use titan_list_templates to discover what titan_run_template can execute. It reads a fixed allowlist, so an agent can never see or reach templates that are hidden, admin-only, inactive, or experimental. This tool starts no run, consumes no credits, and returns immediately. Required scope: none beyond connecting with an mcp:* key.

Parameters

All parameters are filters. Omit them all to see the full allowlist.
string
generic for general-purpose templates, platform for site-specific ones.
string
search, scrape, crawl, or api_call.
string
A search platform identifier, or generic for platform-independent templates. Omit this filter to see every provider available to your account.
string
Free-text match against template slug, name, and description.
boolean
default:"true"
Set false to see only generic templates.
integer
default:"20"
Maximum templates to return.

Example

Response

Template fields

input_schema tells your agent exactly what belongs in payload, and output_schema tells it what records to expect back. An agent that reads both before calling titan_run_template rarely gets a validation error.

The allowlist

Eight templates are runnable through MCP: one search template per supported platform, plus three generic templates. Search templates follow the titan-<platform>-search-v1 pattern and share an identical input and output contract, so an agent can switch platforms without changing how it reads results. Call this tool with action_type: "search" to get the exact slugs available to your account.
The search, fetch, and crawl tools already run these templates for you with friendlier parameters. Reach for titan_run_template only when you need to pass template-specific payload fields the dedicated tools do not expose.

Slug versioning

The -v1 suffix is a contract version, not a release number. A template’s input or output schema will not change incompatibly under the same slug—an incompatible change ships as a new slug. Pin the slug your agent depends on and it keeps working.

Next steps