Skip to main content
Glama
nextafter-michael

unofficial-vwo-mcp-server

List VWO campaigns

vwo_list_campaigns
Read-only

List campaigns in a VWO workspace to retrieve campaign IDs. Filter by type, platform, status, or label to narrow results.

Instructions

List campaigns (experiments) in a VWO workspace. Use this to discover campaign ids before calling any tool that operates on a specific campaign. Filter by type, platform, or label to narrow large accounts.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoFilter by campaign type. VWO's values are lowercase and hyphenated, not the generic A/B-testing names they resemble: "ab", "split" (Split URL), "multivariate" (not "mvt"), "feature-rollout" (Web Rollout), "feature-test", plus non-testing types like "heatmap", "survey", "recording".
labelNoFilter by label name.
limitNoMaximum campaigns to return. VWO caps this endpoint at 25 regardless of what you request, so page through with offset/nextOffset rather than a bigger limit.
offsetNoNumber of items to skip, for paging.
statusNoFilter by campaign status. UPPERCASE only — VWO rejects lowercase with HTTP 400. Omit to get campaigns of every status (which is usually what you want; note that includes DELETED ones, so check each result's own `status` field before reporting a campaign as live). This parameter is absent from VWO's published docs but is real and enforced — the valid values above come from the error message VWO returns for an invalid one.
platformNoFilter by platform: "website", "full-stack", or "mobile-app" (not "WEB"/"FULLSTACK").
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.
projectIdNoFilter by project id.
workspaceNameNoWorkspace name to resolve to an id, as an alternative to accountId. Must match exactly one visible workspace, otherwise an error lists the candidates.
showDetailedInfoNoReturn the full campaign objects instead of a summary. Much larger responses.
Behavior5/5

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

Discloses API cap at 25, pagination via offset/nextOffset, uppercase-only status parameter, inclusion of deleted campaigns by default, and accountId necessity. All beyond the readOnlyHint and openWorldHint annotations, with no contradictions.

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?

Well-structured with purpose first, then usage, then parameters. All sentences add value, but some parameter descriptions are lengthy; still justified given complexity.

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

Completeness5/5

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

Given 10 parameters, no required ones, no output schema, but annotations cover safety and open world. Description covers usage, pagination, special quirks, and parameter details completely. No missing critical information.

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?

Schema coverage is 100%, but each parameter description adds significant value: explains type value format, status case-sensitivity, limit cap, accountId vs workspaceName usage, and platform values. Provides crucial context not present in 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?

Description clearly states the tool lists campaigns (experiments) in a VWO workspace, specifies it for discovering campaign IDs before using specific campaign tools, and distinguishes from siblings by mentioning filtering capabilities.

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?

Explicitly recommends using this to discover campaign IDs before specific campaign operations, and advises filtering for large accounts. Implicitly suggests alternatives like get_campaign when IDs are known, but does not explicitly list when not to use.

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