Skip to main content
Glama
mrh-is

partiful-mcp

by mrh-is

get_my_saved_events

Read-onlyIdempotent

Fetch your saved or bookmarked Partiful events. View events you've explicitly saved for later, separate from RSVPs, followed events, or public invites.

Instructions

Get your saved/bookmarked Partiful events, as an events array. These are events you've explicitly saved for later, distinct from get_discoverable_events (open invite public events), get_my_followed_events (events from people/pages you follow), and get_my_rsvps (events you've been invited to or RSVPed to).

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 readOnly, openWorld, idempotent, and non-destructive traits. The description adds useful context about the semantic scope ('explicitly saved for later') and the return shape ('as an events array'), though it doesn't detail pagination or ordering. Given strong annotation coverage, this is sufficient and adds value beyond the structured data.

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?

Two sentences, no filler. The first sentence front-loads the verb+resource+output shape, and the second sentence provides essential sibling disambiguation. Every word earns its place.

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?

With a single optional parameter, a complete output schema, and rich annotations indicating a safe read operation, the description fully covers the necessary context. It explains what the tool returns and when to use it, so no gaps remain.

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?

Schema description coverage is 100%, with the 'fields' parameter fully documented via a list of all available dot-paths. The description does not mention parameters, so it adds no additional meaning, but the schema already carries the burden. 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 identifies the resource ('your saved/bookmarked Partiful events') and the action ('Get'), and explicitly distinguishes it from three named sibling tools. This makes the tool's 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 gives explicit when-to-use guidance by contrasting with get_discoverable_events, get_my_followed_events, and get_my_rsvps, explaining exactly what each alternative returns. This is the gold standard for sibling differentiation.

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