Skip to main content
Glama
Sign In
vercel-mcp-pro

vercel-mcp-pro

by helbertparanhos
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_aliases

List custom URL aliases for your Vercel account or team, with optional filtering by project ID and limit control.

Instructions

List aliases (custom URLs) in the account/team, optionally filtered by project.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_aliases"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdNoFilter aliases by project id.
limitNoMaximum number of items to return.
teamIdNoTeam ID to scope the request. Falls back to VERCEL_TEAM_ID when omitted.
slugNoTeam slug to scope the request (alternative to teamId).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must fully convey behavior. It only states a read operation but lacks details on pagination, rate limits, default limits, or whether the result is paginated. This is minimal for a list 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?

The description is a single, front-loaded sentence with no wasted words. It efficiently states the action and a key option.

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

Completeness3/5

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

For a simple list tool with a 4-parameter schema at 100% coverage, the description is adequate. However, it omits information about pagination or default limit behavior, which would be helpful for an agent.

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%, so baseline 3 applies. The description adds no extra meaning beyond the schema; it only mentions 'optionally filtered by project' which mirrors the projectId parameter. No additional context for limit, teamId, or slug.

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 aliases (custom URLs)' with a specific verb and resource. It distinguishes from siblings like get_alias (singular) and delete_alias (delete).

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 implies listing multiple aliases but doesn't explicitly guide when to use this tool versus alternatives like get_alias for a single alias or assign_alias for modifications. No when-not or alternative suggestions are given.

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