Gizmo Analytics

create_goal

Define conversion goals for your site by specifying a URL path prefix or a custom event name. Track conversions and rates directly on your dashboard.

Instructions

Create a conversion goal for a site. type='path' matches sessions that visit a path-prefix; type='event' matches sessions that fire a named custom event. Use this when the user says 'track signups as a goal', 'add a goal for /thank-you', etc. Goals show up on the site dashboard with conversion count + rate.

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": {
      "site_id": "<site_id>",
      "name": "<name>",
      "type": "<type>",
      "target": "<target>"
    },
    "name": "create_goal"
  }
}

Input Schema

Name	Required	Description
`site_id`	Yes	Internal site UUID for the target site. Get one from list_sites.
`name`	Yes	Human-readable name for the goal (e.g. 'Signup', 'Purchase').
`type`	Yes	'path' matches sessions that visit a URL path prefix; 'event' matches sessions that fire a named custom event.
`target`	Yes	When type='path', the URL path prefix (e.g. '/thank-you'). When type='event', the event name (e.g. 'signup').

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 20, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already indicate it is not read-only (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds that goals appear on the dashboard with conversion count and rate, providing extra behavioral context, but does not elaborate on side effects or prerequisites.

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?

The description is concise with two sentences plus an example usage sentence. It is front-loaded with the main action and efficiently conveys necessary information without verbosity.

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?

Given the 4 required parameters with full schema coverage, annotations, and existence of an output schema, the description is fairly complete. It explains the two modes and the outcome. It could be slightly more complete by mentioning prerequisites or potential errors, but overall adequate.

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%, so the schema already documents all parameters. The description reinforces the meaning of 'type' and 'target' with examples, but does not add significant new meaning beyond the schema.

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?

The description clearly states 'Create a conversion goal for a site' and differentiates between the two types ('path' and 'event') with examples. It is distinct from siblings like delete_goal and list_goals.

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?

The description provides specific user statements that trigger using this tool ('track signups as a goal', 'add a goal for /thank-you'), giving clear context. However, it does not explicitly mention when not to use it or compare to alternatives like create_funnel.

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