Vaneform

monitor_research

Monitor a Google Ads or AdSense query daily or weekly. Record newly observed public ads and connected sites as private in-app notifications. The first successful observation establishes a baseline. Free; 0 credits.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>",
      "label": "<label>",
      "interval_days": "<interval_days>"
    },
    "name": "monitor_research"
  }
}

Input Schema

Name	Required	Description	Default
`label`	Yes
`query`	Yes
`interval_days`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 6, 2026

addedInput schema / properties / query / properties

Added value: +{
+  "mode": {
+    "enum": [
+      "domain",
+      "advertiser",
+      "publisher"
+    ],
+    "type": "string"
+  },
+  "q": {
+    "maxLength": 3000,
+    "type": "string"
+  },
+  "region": {
+    "type": "string"
+  },
+  "tool": {
+    "enum": [
+      "google-ads",
+      "adsense"
+    ],
+    "type": "string"
+  }
+}

addedInput schema / properties / query / required
```
Added value: +[
+  "tool",
+  "q"
+]
```

First observedOct 15, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations, the description carries the full burden and does supply real behavior: it creates private in-app notifications (a persistent side effect), the first successful observation sets a baseline rather than alerting, and it costs 0 credits. It omits prerequisites, what happens on repeated failures, and how to stop an existing monitor (likely via manage_research).

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

Conciseness4/5

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

Three short sentences, front-loaded with the action, then side effect, then baseline semantics, then cost. 'Free; 0 credits' is slightly redundant but the cost signal is worth stating; nothing else is padding.

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?

No output schema and no annotations, so the description must cover the whole surface; it covers purpose, notification behavior, baseline, and cost, but leaves the nested query shape and label semantics unexplained. Adequate to recognize the tool, insufficient to fill in the query without guessing.

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

Parameters2/5

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

Schema description coverage is 0%, and the description only clarifies one thing: 'daily or weekly' maps to interval_days 1/7. The nested query object — tool, q, mode (domain/advertiser/publisher), region — and the label field get no explanation at all, leaving the most ambiguous part of the call undocumented.

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 and resource ('Monitor a Google Ads or AdSense query daily or weekly') plus the effect ('Record newly observed public ads and connected sites as private in-app notifications'). This is clearly distinguishable from one-shot siblings like lookup_domain or research_site, though no sibling is named explicitly.

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 'daily or weekly' framing implies this is the recurring option versus the one-off research/lookup siblings, but the description never says when to prefer it or when not to. An agent must infer the alternative from the sibling list rather than being routed.

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

All Vaneform 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?