Skip to main content
Glama
Sign In
UnClick MCP Server

UnClick MCP Server

by malamutemayhem
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

vercel_create_env

Create or update environment variables on a Vercel project, with defaults for production, preview, and development targets. Set plain, encrypted, or sensitive values to configure project environments.

Instructions

Create (or upsert) an environment variable on a Vercel project. Target defaults to production, preview, and development. Use type='plain' for non-secret values, 'encrypted' or 'sensitive' for secrets.

Input Schema

NameRequiredDescriptionDefault
keyYes
typeNoplain | encrypted | sensitive | secret | system. Defaults to plain.
valueYes
targetNoCSV of environments: 'production,preview,development'. Defaults to all three.
teamIdNoAlias for team_id.
upsertNoOverwrite existing value for same key/target. Default true.
api_keyNo
commentNo
team_idNo
gitBranchNoAlias for git_branch.
projectIdNoAlias for project_id.
git_branchNo
project_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.11
    • addedInput schema / properties / gitBranch
      Added value: +{
+  "description": "Alias for git_branch.",
+  "type": "string"
+}
    • addedInput schema / properties / projectId
      Added value: +{
+  "description": "Alias for project_id.",
+  "type": "string"
+}
    • addedInput schema / properties / teamId
      Added value: +{
+  "description": "Alias for team_id.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "project_id",
-  "key",
-  "value"
-]New value: +[
+  "key",
+  "value"
+]
  2. Addedv0.1.5

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the operation creates or upserts, that target defaults to all three environments, and when to use secret vs non-secret types, but it omits auth requirements, permission scope, and the destructive implications of overwriting an existing secret.

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 three sentences, front-loaded with the core action and followed by useful defaults and type guidance. There is no wasted text and the structure is easy to scan.

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

Completeness2/5

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

For a 13-parameter mutation tool with no annotations and no output schema, the description is incomplete. It does not explain how to identify the project/team, where api_key comes from, or how aliases like projectId/project_id interact, which an agent needs in order to invoke the tool correctly.

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 description coverage is 46%, so the description should compensate for gaps. It explains the important target and type parameters and implies key/value usage, but it does not clarify api_key, comment, team/project aliases, or git branch scoping, leaving several parameters undocumented.

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 uses a specific verb and resource: 'Create (or upsert) an environment variable on a Vercel project.' It clearly distinguishes the tool from siblings like vercel_get_env and vercel_delete_env by stating that this is the creation/upsert operation.

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?

Usage is implied by the tool name and the action described, and the description gives guidance on type selection. However, it does not explicitly say when to use this tool versus vercel_get_env or vercel_delete_env, nor does it state prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools