Skip to main content
Glama
Sign In

Meetup MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

List RSVPs in Meetup

meetup_list_rsvps
Read-onlyIdempotent

List RSVPs 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_list_rsvps"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/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 the description meaningfully adds that it 'opens nothing by itself' — the key behavioral fact for a guide tool. The API-access caveat adds useful environmental context, though it does not describe the shape of the returned guide beyond 'screens, buttons, fields'.

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?

Purpose is front-loaded and the no-side-effects warning is well placed, but 'from ChatGPT, Claude or any AI agent' is filler, and the trailing GraphQL/Pro-subscription sentence is long and only tangentially relevant to invoking this specific tool.

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 parameters and no output schema, the description covers the essentials: what it returns, that it performs no action, and which tools execute the steps. Only the exact output format of the guide (and scope limits, e.g. which RSVPs) is left implicit.

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 nothing for the description to disambiguate and the baseline applies. It correctly does not invent parameter guidance.

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 (RSVPs in the user's own Meetup account) and clarifies the crucial nuance that the tool returns step-by-step instructions rather than performing the listing itself — a distinction the name alone would obscure. It is slightly undercut by the title/name implying an action, so the agent must read the body to learn the tool is a guide.

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 explicitly says to follow the returned steps with cotlet_browser_* tools in the user's Meetup Cloud Browser, which routes the agent to the right siblings. The note about Meetup Pro API access explains why this guide route exists, but it never states when *not* to call this tool (e.g. for other Meetup tasks like events).

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