Skip to main content
Glama

impri_create_watcher_from_preset

Create a watcher from a preset template using a preset ID and parameter values. The preset manages configuration like URL and keywords; optionally override the schedule or name.

Instructions

Create a watcher from a preset template by supplying the preset id and param values.

Presets handle all watcher config construction — URL building, keyword setup, SSRF validation — so you only provide the param values listed by impri_list_watcher_presets.

The schedule defaults to the preset's recommended interval but can be overridden. The name defaults to "{preset title}: {primary param value}" if omitted.

Returns { watcher_id, name, kind, status, next_run_at }.

Examples:

Watch the HN front page (no params needed): preset_id: "hn-front-page" params: {}

Watch a subreddit for new posts: preset_id: "reddit-subreddit" params: { subreddit: "MachineLearning" }

Watch a GitHub repo for new releases, check every 2 hours: preset_id: "github-releases" params: { owner: "fastify", repo: "fastify" } schedule: { every: "2h" }

Watch HN for keyword with a custom min_points threshold: preset_id: "hn-keyword" params: { keyword: "rust programming", min_points: "25" }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoOptional display name for the watcher. Defaults to "{preset title}: {primary param value}" when omitted.
paramsYesKey/value map of param values as strings. Required params must be present; optional params may be omitted to use preset defaults.
scheduleNoOptional schedule override. Omit to use the preset's default schedule.
preset_idYesPreset identifier from impri_list_watcher_presets (e.g. "hn-front-page", "reddit-subreddit", "github-releases").
Behavior5/5

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

With no annotations, the description fully discloses behavior: schedule/naming defaults, SSRF validation, config construction by presets, and return structure. No contradictions.

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?

Well-structured: summary, details, then four diverse examples. Every sentence adds value, no fluff.

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 4 params with nested objects and no output schema, description covers return fields, defaults, and parameter behavior comprehensively with examples.

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?

Schema coverage is 100% (baseline 3). Description adds meaning by explaining param type (key/value map of strings), requirement rules, and schedule override semantics.

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?

Clearly states it creates a watcher from a preset template, specifies what presets handle (URL building, keyword setup, SSRF validation), and differentiates from siblings like impri_create_watcher and impri_list_watcher_presets.

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

Usage Guidelines4/5

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

Explains when to use the tool (have a preset ID and params) and references impri_list_watcher_presets for param definitions, but lacks explicit when-not-to-use or direct mention of alternative tools.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/sekera-radim/impri'

If you have feedback or need assistance with the MCP directory API, please join our Discord server