vercel-mcp-pro

create_log_drain

Create a log drain to ship logs from specified sources (build, edge, lambda, static, external) to your HTTPS endpoint with configurable delivery format (json, ndjson, syslog).

Instructions

Create a configurable log drain that ships logs to your endpoint. Choose the sources (build, edge, lambda, static, external) and delivery format.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>",
      "url": "<url>",
      "sources": "<sources>"
    },
    "name": "create_log_drain"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Drain name.
`url`	Yes	HTTPS endpoint to deliver logs to.
`deliveryFormat`	No
`sources`	Yes	Which log sources to drain.
`projectIds`	No	Limit to specific projects.
`headers`	No	Custom headers to send.
`secret`	No	Signing secret for verifying delivery.
`teamId`	No	Team ID to scope the request. Falls back to VERCEL_TEAM_ID when omitted.
`slug`	No	Team slug to scope the request (alternative to teamId).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 11, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations provided, so description must bear the burden. It describes a mutation (create) but doesn't disclose behavioral traits like idempotency, rate limits, side effects on existing resources, or auth requirements. The description is brief and lacks behavioral detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Two short sentences with front-loaded action. However, the list of sources is incomplete ('firewall' missing), which is a minor inaccuracy. That prevents a perfect score. Overall, it's concise and structured well.

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 creation tool with 9 parameters (3 required) and no output schema, the description is too minimal. It doesn't explain return values, error scenarios, or the purpose of optional fields (secret, headers, teamId). The agent lacks context to invoke the tool correctly in complex scenarios.

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 high (89%), so baseline is 3. The description adds some value by listing possible sources, but it omits 'firewall' from the schema's enum, making it incomplete. It doesn't explain additional parameters like secret, headers, or projectIds beyond the schema.

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 action (create) and the resource (log drain), and mentions key configurable aspects (sources, delivery format). It distinguishes itself from sibling tools like delete_log_drain and list_log_drains by focusing on creation.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives. It doesn't mention prerequisites (e.g., team context), idempotency, or scenarios where creation might fail. Sibling tools like list_log_drains exist but no usage advice.

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

Deploy Server