Skip to main content
Glama
mrh-is

partiful-mcp

by mrh-is

get_my_followed_events

Read-onlyIdempotent

Retrieve Partiful events you follow from hosts and pages, including those you haven't RSVPed to. Get an array of followed events with optional field selection.

Instructions

Get Partiful events you're following, as an events array. Following tracks events from hosts/pages you follow without necessarily RSVPing, distinct from get_my_saved_events (explicitly bookmarked events), get_discoverable_events (open invite public events), 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 readOnlyHint/openWorldHint/idempotentHint and destructiveHint=false, so safety is covered. The description adds meaningful behavioral context beyond annotations by defining what 'following' means (events from hosts/pages followed without necessarily RSVPing) and by clarifying the event array return. It doesn't cover pagination or rate limits, but the low-risk read-only nature plus semantic context justifies a 4.

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 fluff. The first sentence front-loads the primary purpose and output; the second sentence efficiently disambiguates from sibling tools. Every phrase 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?

Given the tool's simplicity (one optional param, read-only, output schema present), the description fully covers the necessary context: what the tool returns, the semantics of 'following', and differentiation from closely related tools. The schema documents parameters and output, so no further return-value explanation is needed.

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', has a detailed description in the schema with a full list of dot-path field names and instructions to omit for all fields. Schema coverage is 100%, so the description correctly does not add extra parameter details. Baseline 3 applies because the description adds no parameter-specific semantics beyond the schema.

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 uses a specific verb ('Get') and resource ('Partiful events you're following'), clearly stating the output format ('as an `events` array'). It explicitly distinguishes the tool from get_my_saved_events, get_discoverable_events, and get_my_rsvps, making the purpose unambiguous even among many siblings.

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?

It provides explicit when-to-use guidance by naming three alternative tools and their semantics: saved events (bookmarked), discoverable events (public invite), and RSVPs (invited/RSVPed). This tells the agent exactly when to choose this tool over those alternatives.

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