webdata-tools-mcp

Get trade show exhibitor lists (booths and contacts)

get_trade_show_exhibitors

Read-onlyIdempotent

Extract exhibitor lists from trade shows as B2B leads with company, booth, email, phone and website. Provide built-in show IDs or any exhibitor-list link to pull structured contact data.

Instructions

Exhibitor lists of trade shows as B2B leads: company, booth and hall, email, phone, website, address, socials and categories. 91 built-in shows (e.g. medica, sema-show, nab-show, fabtech, ish, automechanika, wtm-london, orgatec, eurotier, wine-paris, biofach) or any exhibitor-list link or show homepage on Messe Frankfurt, Messe Düsseldorf, Koelnmesse, NürnbergMesse, Newfront/ExpoPlatform, RX, Map Your Show, a2z / A2Z Connect, Swapcard or Corussoft; the link's own show and year are used. Contact coverage depends on what the organiser publishes. Runs the Apify Actor tacps126/exhibition-scraper on your Apify account (about $0.002 per exhibitor; spend per call is capped at $0.5).

Input Schema

Name	Required	Description
`urls`	No	Links to any show's exhibitor list or exhibitor search page (or its homepage).
`shows`	No	Built-in show ids, e.g. ["medica","sema-show"]. The Actor README lists all ids.
`max_items`	No	Maximum results to return (default 50, max 2000). Cost scales with this.
`extra_input`	No	Advanced: extra Actor input fields, merged over the defaults.
`changes_only`	No	Only exhibitors that are new, changed (old and new booth, email, phone, website, address) or removed since the last call with the same shows. Removed ones need the whole list, so it ignores max_items for that.
`include_contacts`	No	Open each exhibitor profile for email, phone, website, address and socials. Off = names and booths only (faster).

Output Schema

Name	Required	Description
`tool`	Yes	Name of the tool that produced the result.
`count`	Yes	Number of records the Actor returned.
`items`	Yes	The records. Long text fields are shortened to 600 characters.
`shown`	Yes	Number of records included in `items` (can be lower than count when the result is long).
`truncated`	Yes	True when records were left out to keep the result short; ask for fewer items.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.10.1Oct 23, 2026

addedInput schema / properties / changes_only

Added value: +{
+  "default": false,
+  "description": "Only exhibitors that are new, changed (old and new booth, email, phone, website, address) or removed since the last call with the same shows. Removed ones need the whole list, so it ignores max_items for that.",
+  "type": "boolean"
+}

Addedv0.4.0Oct 20, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the readOnly/openWorld/idempotent annotations by disclosing the underlying Apify Actor, per-exhibitor pricing (~$0.002), a hard $0.5 spend cap per call, and the caveat that contact coverage depends on what the organiser publishes. Those are exactly the cost and reliability facts an agent needs before invoking a paid scrape.

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?

Three sentences, front-loaded with what is returned and then the sources. The long enumerations of 11 shows and 9 platform names are dense but earn their place by signalling coverage; slight trimming would still leave room for an explicit alternative.

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 full output schema, rich annotations and 100% parameter coverage, the description still supplies the cost model, source universe and data-quality caveat, leaving nothing an agent needs in order to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3; the description still adds value by giving concrete show-id examples, explaining that a URL's own show and year are used, and tying cost to result volume. It doesn't add much for extra_input or changes_only beyond what the schema already states.

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?

Names a specific verb+resource (exhibitor lists of trade shows as B2B leads) and immediately enumerates the returned fields (company, booth/hall, email, phone, website, address, socials, categories). This clearly separates it from sibling lead/research tools like find_website_contacts and find_events.

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

Usage Guidelines4/5

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

Explains the two input modes in detail: 91 built-in show ids, or any exhibitor-list URL or show homepage, with the show and year inferred from the link. It does not explicitly say when to choose this over siblings such as find_website_contacts, so the routing guidance is clear but not exhaustive.

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