Skip to main content
Glama
nextafter-michael

unofficial-vwo-mcp-server

Remove a label from a VWO campaign

vwo_delete_campaign_label
DestructiveIdempotent

Detach a label from a VWO campaign by providing the campaign ID and label ID. The label remains in the workspace but is no longer associated with the campaign.

Instructions

Remove one label from a VWO campaign. This detaches the label from the campaign; it does not delete the label from the workspace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelIdYesLabel id to remove. Call vwo_list_campaign_labels if you do not have it.
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?

The description adds important context beyond annotations: it clarifies that detaching does not delete the label from the workspace, which is not evident from the annotations alone (destructiveHint=true indicates deletion but here it's a relationship removal). This helps an agent understand the actual scope of the operation.

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, zero wasted words. Front-loaded with the core action, followed by a crucial clarification. Every sentence earns its place.

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 simple tool with full schema annotations, the description is adequate. It clarifies the non-destructive nature regarding the label itself and explains the single-label removal. No output schema exists, so return values are not expected; however, a brief note on the result (e.g., success/failure) could enhance completeness.

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 100% and each parameter already has descriptive text (e.g., 'Call vwo_list_campaign_labels if you do not have it'). The tool description does not add further parameter-level detail, but the schema fully covers semantics, so baseline 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 the tool removes a label from a VWO campaign, using specific verb 'Remove' and resource 'label from a VWO campaign'. It distinguishes from siblings like vwo_add_campaign_label (adds) and vwo_list_campaign_labels (lists).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implicitly indicates when to use the tool (to detach a label from a campaign) and clarifies what it does not do (delete the label), but it does not explicitly compare with alternatives or provide when-not-to-use guidance.

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