Skip to main content
Glama
nextafter-michael

unofficial-vwo-mcp-server

List VWO labels

vwo_list_labels
Read-only

List all labels in a VWO workspace with their ids. Use this to find a label id before applying it to a campaign or filtering campaigns by label.

Instructions

List all labels defined in a VWO workspace, with their ids. Use this to find a label id before applying it to a campaign, or to filter vwo_list_campaigns by label.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of items to return.
offsetNoNumber of items to skip, for paging.
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.
workspaceNameNoWorkspace name to resolve to an id, as an alternative to accountId. Must match exactly one visible workspace, otherwise an error lists the candidates.
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the description need not restate safety. It adds that labels come with ids, but no behavioral traits beyond what annotations convey. 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.

Conciseness5/5

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

Two sentences, front-loaded with the main action. Every word earns its place; no redundancy.

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?

The tool is simple, annotations are present, schema is fully covered. The description, though brief, is complete for the tool's purpose and context.

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 covers 100% of parameters with descriptions; the description adds no parameter-level info beyond what's in the schema. Baseline score of 3 is appropriate.

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 'List all labels defined in a VWO workspace, with their ids,' which is a specific verb-resource pair. It distinguishes from sibling tools like vwo_list_campaign_labels by mentioning applying to campaigns.

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 explicitly states when to use this tool: 'find a label id before applying it to a campaign, or to filter vwo_list_campaigns by label.' It provides context but does not list scenarios where it should not be used or compare to all siblings.

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