Skip to main content
Glama
Sign In

Meetup MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Create event in Meetup

meetup_create_event
Read-onlyIdempotent

Create event in the user's own Meetup account from ChatGPT, Claude or any AI agent. Returns how to do it in Meetup step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Meetup Cloud Browser. Meetup's official API: Meetup has a GraphQL API, but only members with an active Meetup Pro subscription can get access, and it stops working when Pro lapses (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": "meetup_create_event"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, and the description stays consistent by stating it 'opens nothing by itself'. It adds useful context annotations cannot convey: the return value is human-style UI instructions (screens, buttons, fields), and the note about Meetup Pro-only GraphQL API explains why browser automation is required.

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 core behavior is front-loaded, but phrases like 'from ChatGPT, Claude or any AI agent' are filler that consume space without helping tool selection. The API-access caveat is relevant but placed after the actionable instruction, so its value is diluted.

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 zero-parameter, no-output-schema guide tool, the description covers what it returns and what to do next. However, it doesn't say how to supply the event details (to the agent itself, presumably) or how the instructions are scoped to the user's account, which leaves a small but real gap in the workflow.

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 there is no parameter semantics for the description to add. The baseline of 4 applies; the description correctly implies no inputs are needed.

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 and verb (create a Meetup event) and immediately clarifies the actual behavior: it returns step-by-step instructions rather than performing the action. The name 'create_event' slightly oversells what happens, but the second clause corrects that within the same sentence.

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 usage chain: call this first to get the steps, then execute them with the cotlet_browser_* tools. It doesn't contrast with sibling tools like meetup_copy_event or say when not to use this, but the guidance for the typical flow is explicit.

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

All Meetup MCP Server and API by Cotlet toolsInspect
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