Skip to main content
Glama
MacKitchin

Informa Events Directory MCP Server

by MacKitchin

get_informa_events_with_details

Enrich directory events with event-page details such as JSON-LD, offers, and contact hints, using controlled concurrency for bulk operations.

Instructions

Bulk-enrich directory events with event-page details (JSON-LD/offers/contact hints) using controlled concurrency.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateToNoOptional upper bound ISO date (YYYY-MM-DD) applied after directory retrieval.
dateFromNoOptional lower bound ISO date (YYYY-MM-DD) applied after directory retrieval.
entryUrlNoEntry URL used for HTML fallback pagination.https://informaconnect.com/events/?subBrands%5B0%5D=Informa%20Connect&availableSubBrands%5B0%5D=Informa%20Connect&requestedSortType=FEATURED&page=1&count=20&searchInput=&type%5B0%5D=EVENT
maxPagesNoPagination safety cap.
pageSizeNoNumber of directory items per page.
startPageNoStarting page index.
monthFilterNoFilter by month facet values, e.g. 'March 2026'.
resultLimitNoOptional cap on directory events before detail enrichment.
searchInputNoKeyword query string.
responseModeNoOutput shape. 'slim' and 'summary' return reduced field sets.full
topicsFilterNoFilter by topic facet values.
countryFilterNoFriendly alias for country-level location filtering. Merged into locationFilter.
includeFacetsNoWhen true, request facet payloads from discovery API. Disable for smaller responses.
sectorsFilterNoFilter by sector facet values.
locationFilterNoFilter by location facet values.
subBrandFilterNoFilter by sub-brand(s).
detailMaxEventsNoMaximum number of events to enrich with detail pages.
eventTypeFilterNoFilter by type(s). Defaults to EVENT.
detailConcurrencyNoNumber of concurrent event-page detail fetches.
forceHtmlFallbackNoSkip API and parse directory pages from embedded Redux state.
requestedSortTypeNoSort order requested from discovery API.FEATURED
stopOnDetailErrorNoWhen true, stop remaining detail fetches after the first detail error.
deliveryTypeFilterNoFilter by delivery type values, e.g. PHYSICAL, VIRTUAL.
Behavior2/5

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

No annotations provided, so description bears full burden. Mentions 'controlled concurrency' but does not disclose potential side effects like rate limiting, failure modes, or data mutability. Lacks detail on behavior beyond a high-level summary.

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

Conciseness4/5

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

Description is a single sentence with relevant keywords (bulk-enrich, JSON-LD, offers, contact hints, controlled concurrency). Efficient but could include brief additional context without harming conciseness.

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

Completeness2/5

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

Given 23 parameters, no output schema, and no annotations, the description is insufficient. It does not explain return values, error handling, or detail enrichment process. Lacks completeness for a complex tool.

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 coverage is 100%, so baseline is 3. Description does not add additional meaning beyond the schema; the schema already describes parameters well. No extra context provided by description.

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?

Description uses specific verb 'bulk-enrich' and resource 'directory events' with explicit detail types (JSON-LD/offers/contact hints) and a distinguishing feature (controlled concurrency). Clearly differentiates from sibling 'get_informa_event_speakers' which focuses on speakers.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives, no conditions for use, no prerequisites, and no mention of when not to use it. The description implies usage for enriching events but lacks explicit direction.

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/MacKitchin/informa-events-directory-mcp-server'

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