Skip to main content
Glama

Tomorrow Central: Cloud Cost Sentinel

Set the conversions counted

webops_set_conversions
Destructive

Sets which Analytics events count as conversions for one of the organization's websites, and the paths whose events are left out. Conversions are re-read from Analytics with the next refresh. Nothing happens until the person confirms: this returns a summary and a code for tc_confirm.

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": {
      "domain": "<domain>",
      "events": "<events>",
      "exclude_paths": "<exclude_paths>"
    },
    "name": "webops_set_conversions"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes
eventsYesOne Analytics event name per line; the counted set becomes exactly these (none: the property's key events count).
exclude_pathsYesOne path prefix per line (e.g. /careers) whose events are not leads; the set becomes exactly these.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false; the description goes further by disclosing the delayed effect (re-read at the next refresh) and the mandatory human-confirmation handshake returning a summary and tc_confirm code. It does not explicitly say that the current conversion configuration is overwritten, which matters for a destructive tool.

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?

Three short sentences, each carrying distinct information: scope, refresh timing, and confirmation gating. Front-loaded with the core action and no redundant restatement of the title.

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

Completeness4/5

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

For a destructive, non-idempotent setter with three required params and no output schema, the description covers the two non-obvious behaviors an agent needs, namely deferred effect and the confirm step. It falls short only on the permissions and overwrite consequences of replacing the existing conversion set.

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 coverage is 67%; events and exclude_paths already carry descriptions, and domain is only constrained by pattern and length. The description loosely identifies domain as 'one of the organization's websites' but adds no format, matching, or replacement semantics beyond what the schema states.

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: which Analytics events count as conversions for one of the organization's websites, plus the excluded paths. It is far more specific than the title alone, but it never names or contrasts a sibling such as webops_set_goal or webops_set_funnel_steps, so the agent must infer the boundary.

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?

Gives clear procedural guidance for invocation: conversions are re-read at the next Analytics refresh, and nothing happens until the person confirms via the returned tc_confirm code. That is real when/how-to-use context, but it offers no exclusions or comparison against the other webops_set_* configuration tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources