Skip to main content
Glama
mrh-is

partiful-mcp

by mrh-is

get_discoverable_events

Read-onlyIdempotent

Retrieve publicly discoverable Partiful events shown on the 'Open invite' tab, including ones you weren't invited to or RSVPed for.

Instructions

Get open-invite / discoverable Partiful events for the home page 'Open invite' tab, as an events array. Unlike get_my_rsvps/get_my_upcoming_events_for_home_page/get_my_past_events_for_home_page/get_published_events, these events aren't necessarily ones you've been invited to or RSVPed to — they're publicly discoverable events surfaced to you. Distinct from get_my_saved_events (events you've explicitly bookmarked) and get_my_followed_events (events from people/pages you follow).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNoDot-path field names to include in the response. Omit to return all fields. Available fields: events, events.allowGuestPhotoUpload, events.attendedGuestCount, events.calendarFile, events.displaySettings, events.displaySettings.effect, events.displaySettings.theme, events.displaySettings.titleFont, events.endDate, events.guest, events.guest.eventId, events.guest.id, events.guest.status, events.guest.userId, events.guestStatusCounts, events.guestStatusCounts.DECLINED, events.guestStatusCounts.GOING, events.guestStatusCounts.INTERESTED, events.guestStatusCounts.MAYBE, events.guestStatusCounts.PENDING_APPROVAL, events.guestStatusCounts.SENT, events.guestStatusCounts.WAITLIST, events.id, events.image, events.image.blurHash, events.image.contentType, events.image.height, events.image.url, events.image.width, events.location, events.locationDisplayText, events.ownerIds, events.showGuestCount, events.showGuestList, events.showHostList, events.startDate, events.status, events.timezone, events.title

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventsNo
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety is covered. The description adds meaningful behavior context: these are publicly discoverable events surfaced to the user, not necessarily tied to invitations or RSVPs, and returns an `events` array. This goes beyond what annotations and schema alone convey, though it doesn't detail auth or rate limits.

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

Conciseness5/5

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

The description is front-loaded with the main purpose in the first sentence, then uses a second sentence to differentiate from a cluster of sibling tools with specific names. Every phrase earns its place, and the length is justified given the many related tools. No fluff or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has a single optional parameter, a rich output schema, and comprehensive annotations. The description fully explains what the events are, where they appear (home page tab), and how they differ from similar tools. There is no missing information about return shape or semantics that would confuse an agent.

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?

The only parameter 'fields' is well-documented in the schema with a comprehensive list of available dot-path fields and the note to omit for all fields. Since schema coverage is 100%, the description doesn't need to add parameter semantics, and it doesn't provide extra value here. Baseline 3 is appropriate.

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 tool gets open-invite / discoverable Partiful events for the home page 'Open invite' tab, returning an `events` array. It explicitly names multiple sibling tools (get_my_rsvps, get_my_upcoming_events_for_home_page, etc.) and differentiates by saying these events aren't necessarily ones you've been invited to or RSVPed to, making the purpose unambiguous.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool versus alternatives: it contrasts with invited/RSVPed event tools, and also distinguishes from get_my_saved_events and get_my_followed_events. This gives clear context for selection without needing to inspect sibling descriptions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mrh-is/partiful-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server