Skip to main content
Glama
Sign In

Meetup MCP Server and API by Cotlet

by dev.cotlet
OverviewDiscussionsAdmin

Message members in Meetup

meetup_message_members
Read-onlyIdempotent

Message members 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_message_members"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, it discloses the critical behavioral fact that the tool opens nothing by itself and only returns guidance, so there is no side effect to guard against. It also explains the external constraint (Meetup's GraphQL API is Pro-only and stops working when Pro lapses), which justifies the browser-based path. This is substantive context the annotations cannot convey.

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 instruction is front-loaded and clear, but the opening clause 'from ChatGPT, Claude or any AI agent' is promotional filler that earns no place. The API/subscription paragraph is genuinely useful but is long enough to bury the actionable instruction.

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?

For a zero-parameter guide tool with no output schema, the description adequately covers what comes back (step-by-step screens, buttons, fields) and how to act on it. It could say more about failure modes, such as what happens if the Cloud Browser session is not authenticated, but nothing essential is missing.

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 is 4. It implicitly confirms no input is required, but adds no detail about how the returned procedure is shaped or filtered by account context.

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 second sentence is explicit that this tool returns step-by-step instructions (screens, buttons, fields) rather than performing the messaging, which corrects the potentially misleading 'Message members' name. It also names the companion cotlet_browser_* family, so an agent can place the tool in a workflow. It stops short of a one-line statement of the resource's scope and does not contrast directly with the meetup_* siblings.

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 pattern: call this to get the procedure, then carry it out with cotlet_browser_* in the user's Meetup Cloud Browser. That is concrete next-step guidance. It does not say when NOT to use it or how it relates to cotlet_app_guide, which is the main gap.

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