FeelingSurf

Create a site template

create_site_template

Create a site template. A template is a reusable bundle of site settings (no url/paused/labels). Only name is required; every other field defaults to a new-template configuration. Exceeding the per-account cap returns 403 template_limit_reached. Fields for creating a site template. Only name is required; all others default to a new-template configuration.

Input Schema

Name	Required	Description
`name`	Yes	Template name.
`limits`	No	Visit caps; null means no limit.
`actions`	No	Auto-actions performed during visits.
`cookies`	No	Cookies to set before each visit; replaces the stored list.
`devices`	No	Device targeting split, as percentages summing to 100.
`browsing`	No	Browsing options.
`schedule`	No	Active-hours scheduling.
`visit_duration`	No	Visit duration range, in seconds.
`blocked_domains`	No	Domains blocked during visits.
`traffic_quality`	No	Traffic quality controls.
`traffic_sources`	No	IDs of traffic sources to assign.
`location_targeting`	No	Country/continent targeting.
`visit_distribution`	No	How visits are paced — "even" spreads them across the day, "asap" delivers as fast as possible.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 11, 2026

removedInput schema / properties / actions / properties / items / items / properties / cookie

Removed value: -{
-  "description": "Present for cookie actions.",
-  "properties": {
-    "domain": {
-      "description": "Domain to set the cookie on.",
-      "type": "string"
-    },
-    "name": {
-      "description": "Cookie name.",
-      "type": "string"
-    },
-    "value": {
-      "description": "Cookie value.",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}

changedInput schema / properties / actions / properties / items / items / properties / type / description

Previous value: -"What the app does — click a link, click an RSS or sitemap link, set a cookie, scroll, or refresh."New value: +"What the app does — click a link, click an RSS or sitemap link, scroll, or refresh."

changedInput schema / properties / actions / properties / items / items / properties / type / enum

Previous value: -[
-  "click",
-  "click_rss",
-  "click_sitemap",
-  "cookie",
-  "scroll",
-  "refresh"
-]New value: +[
+  "click",
+  "click_rss",
+  "click_sitemap",
+  "scroll",
+  "refresh"
+]

addedInput schema / properties / cookies

Added value: +{
+  "description": "Cookies to set before each visit; replaces the stored list.",
+  "items": {
+    "description": "A cookie set on the browser session before the visit begins.",
+    "properties": {
+      "domain": {
+        "description": "Domain to set the cookie on (a leading dot is dropped; subdomains are covered either way); null sets it on the visited site's host.",
+        "maxLength": 256,
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "name": {
+        "description": "Cookie name.",
+        "maxLength": 256,
+        "type": "string"
+      },
+      "value": {
+        "description": "Cookie value.",
+        "maxLength": 256,
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "value"
+    ],
+    "type": "object"
+  },
+  "maxItems": 10,
+  "type": "array"
+}

First observedOct 6, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), so the bar is lower. The description nonetheless adds real behavioral detail beyond the annotations: a per-account cap that produces a 403 `template_limit_reached`. It does not describe what is returned on success, but this is a genuine failure-mode disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two of the four sentences are near-verbatim restatements of the earlier content ('Only `name` is required; every other field defaults to a new-template configuration' appears twice), and the trailing 'Fields for creating a site template' is a filler fragment. The description looks like two concatenated snippets that were never deduplicated.

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

Completeness3/5

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

For a 13-parameter, deeply nested creation tool with no output schema, the description covers the required-vs-defaulted contract and one failure mode, but says nothing about the return value or any permission/authentication prerequisites. Adequate but with clear gaps.

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 the schema documents all 13 parameters in depth, so the baseline is 3. The description only adds the defaulting behavior ('every other field defaults to a new-template configuration') and the observation that url/paused/labels are not part of the bundle, which is modest value over what the schema already conveys.

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?

States a specific verb+resource ('Create a site template') and clarifies the resource by defining it as a reusable bundle of site settings without url/paused/labels, which implicitly separates it from create_site. It never names a sibling tool, but the resource definition is distinctive enough that an agent can distinguish it.

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?

The definition of a template as a 'reusable bundle' plus the note that only `name` is required implies when this is worth calling versus create_site, but there is no explicit when-to-use, when-not-to-use, or alternative-tool routing. Usage must be inferred.

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

All FeelingSurf tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?