Skip to main content
Glama
mrh-is

partiful-mcp

by mrh-is

get_published_events

Read-onlyIdempotent

Retrieve all Partiful events you host, including dates, locations, and guest counts, for any time period. Use this instead of RSVP or time-scoped views to see your hosting activity.

Instructions

Get all Partiful events you are hosting (any time period), as an events array with title, date, location, and guest counts. Use this instead of get_my_rsvps (which covers events you attend/RSVP to, not necessarily host) or get_my_upcoming_events_for_home_page/get_my_past_events_for_home_page (which are home-page views scoped by time, not by host role).

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 read-only, open-world, idempotent, and non-destructive behavior. The description adds valuable behavioral context by specifying that the tool returns events across any time period and summarizing the response structure (events array with title, date, location, guest counts). It does not mention pagination or ordering, but that's beyond what annotations need and the description already adds more than the baseline.

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 two sentences, front-loaded with the verb and scope, then immediately gives alternatives. Every sentence carries necessary information without redundancy, making it efficient and easy to parse.

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 one optional parameter fully covered by the schema, comprehensive annotations, and an output schema present, the description provides sufficient context: it states the purpose, scope, and usage guidance, and doesn't need to repeat return field details. The description enables an agent to select and invoke the tool correctly.

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 fully documented in the input schema with a description and a comprehensive list of dot-path values. Schema coverage is 100%, so the baseline applies. The description adds nothing beyond schema about how to use the parameter; it only mentions example output fields, not parameter usage.

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 action ('Get'), the exact scope ('all Partiful events you are hosting'), and the time range ('any time period'). It also explicitly distinguishes the tool from sibling tools by naming them and explaining the differences (host role vs. attendee, time-scoping).

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 directly instructs when to use this tool over alternatives: 'Use this instead of get_my_rsvps...' and explains why those alternatives are not suitable (attendee status or time-scoped home-page views). This gives clear when-to-use and when-not-to-use guidance.

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