Skip to main content
Glama
nextafter-michael

unofficial-vwo-mcp-server

Delete a VWO campaign section

vwo_delete_campaign_section
DestructiveIdempotent

Permanently remove a section from a VWO campaign. This action alters page areas visitors see and affects reporting, so confirm the section before deletion.

Instructions

Permanently delete a section from a VWO campaign. This cannot be undone. Sections determine which page areas the campaign varies, so changes affect what live visitors see and how combinations are reported. Confirm the specific section with the user before calling.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
sectionIdYesVWO section id. Call vwo_list_campaign_sections first if you do not have it.
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.
Behavior5/5

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

Beyond the destructiveHint=true annotation, the description explicitly states 'cannot be undone' and explains the real-world effect on visitors and reporting. This adds valuable behavioral context beyond what annotations provide.

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 four concise sentences. Each sentence serves a distinct purpose: stating the action, emphasizing irreversibility, explaining impact, and providing usage guidance. No wasted words.

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 covers the key aspects: action, irreversibility, impact on visitors, and user confirmation. While it lacks explicit mention of return value or error handling, the annotations and schema cover safety and parameters adequately.

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?

The input schema already provides 100% coverage with clear descriptions for all parameters. The description does not add new parameter-specific information, so it meets the baseline but does not exceed it.

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 verb 'delete' and the resource 'section from a VWO campaign', and emphasizes permanence. It distinguishes from siblings like vwo_delete_campaign_goal or vwo_update_campaign_section by specifying the exact operation.

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 explains when to use the tool: to permanently remove a section after user confirmation. It warns about impact on live visitors and reporting, guiding appropriate context. However, it does not explicitly mention alternatives or when not to use it.

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