Skip to main content
Glama
nextafter-michael

unofficial-vwo-mcp-server

Create a VWO campaign goal

vwo_new_campaign_goal

Add a new goal to a VWO campaign to define what the experiment measures. Note: modifying goals on a running campaign can invalidate results.

Instructions

Add a new goal to a VWO campaign. Goals define what the experiment measures, so changing them on a running campaign affects reported results and can invalidate conclusions drawn so far.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyYesDefinition of the goal to create. VWO does not publish a schema for this request body; see https://developers.wingify.com/reference/create-a-campaign-goal for the accepted fields. The object is sent to VWO as-is.
accountIdNoNumeric VWO workspace (account) id to operate on. Required unless the server has a default workspace configured. If the user referred to a workspace by name, either pass workspaceName instead or call vwo_list_workspaces to look up the id — never guess an id.
campaignIdYesVWO campaign id. Call vwo_list_campaigns first if you do not have it.
workspaceNameNoWorkspace name to resolve to an id, as an alternative to accountId. Must match exactly one visible workspace, otherwise an error lists the candidates.
Behavior4/5

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

Annotations indicate non-read-only and non-destructive behavior. The description adds beyond this by warning that goals on a running campaign affect reported results and can invalidate conclusions, disclosing side effects.

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?

Two sentences efficiently convey the main action and an important caveat. No wasted words, and the critical warning is front-loaded.

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?

The description explains the goal's purpose and warns of consequences, but lacks information on the return value (e.g., created goal object). Given no output schema, a brief mention of typical response would improve completeness.

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

Parameters5/5

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

All four parameters are described with schema coverage at 100%. The body parameter points to external docs and explains it's sent as-is. accountId and workspaceName provide usage guidance, and campaignId recommends prior listing.

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?

Description clearly states 'Add a new goal to a VWO campaign,' using a specific verb and resource. It distinguishes from sibling tools like vwo_get_campaign_goal and vwo_delete_campaign_goal by focusing on creation.

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 warns that changing goals on a running campaign affects results and can invalidate conclusions, providing clear context for cautious use. However, it does not explicitly state when not to use or list 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/nextafter-michael/unofficial-vwo-mcp-server'

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