Perfect Venue MCP Server and API by Cotlet

List events in Perfect Venue

perfect_venue_list_events

Read-onlyIdempotent

List events in the user's own Perfect Venue account from ChatGPT, Claude or any AI agent. Returns how to do it in Perfect Venue step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Perfect Venue Cloud Browser. Perfect Venue's official API: Perfect Venue has one public API, the Leads API: a write-only endpoint that creates a lead from your own contact form, and only on the Enterprise plan (checked 11 Oct 2026).

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": "perfect_venue_list_events"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Beyond readOnlyHint=true and openWorldHint=false, it discloses the non-obvious behavior that the tool returns instructions rather than data and performs no browser action itself. The additional note about Perfect Venue's Leads API being write-only and Enterprise-only is accurate context but largely unrelated to listing events.

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

Conciseness3/5

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

The first sentence is front-loaded and useful, but roughly half the text is a digression on the Leads API, plan tier and a check date that does not help an agent call this tool. Cutting that would sharpen the definition without losing guidance.

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?

With no output schema, the description does explain the return form (step-by-step screens, buttons, fields) and the follow-up tooling, which is enough for an agent to know what to do with the result. It could mention the prerequisite of an active Cloud Browser session on the user's Perfect Venue account.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4; nothing about parameter meaning needs explaining and the description correctly implies no input is required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the resource (events in the user's own Perfect Venue account) and clarifies the actual deliverable: it 'Returns how to do it in Perfect Venue step by step (screens, buttons, fields)', so the name's 'list events' is not misread as a data query. It does not explicitly distinguish itself from siblings like perfect_venue_list_payments, but the verb+deliverable is unambiguous.

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?

It gives a clear workflow: call this to get the steps, then execute them 'with the cotlet_browser_* tools in the user's Perfect Venue Cloud Browser', and states it 'opens nothing by itself.' It stops short of naming when NOT to use it or how it relates to the other perfect_venue_* siblings.

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

All Perfect Venue MCP Server and API by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?