Skip to main content
Glama
webdata-tools-mcp

webdata-tools-mcp

Get trade show exhibitor lists (booths and contacts)

get_trade_show_exhibitors
Read-onlyIdempotent

Extracts trade show exhibitor lists and contact details from show pages or built-in events to build B2B lead lists for outreach.

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.001 per exhibitor; spend per call is capped at $0.5).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_trade_show_exhibitors"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsNoLinks to any show's exhibitor list or exhibitor search page (or its homepage).
showsNoBuilt-in show ids, e.g. ["medica","sema-show"]. The Actor README lists all ids.
max_itemsNoMaximum results to return (default 50, max 2000). Cost scales with this.
extra_inputNoAdvanced: extra Actor input fields, merged over the defaults.
changes_onlyNoOnly 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_contactsNoOpen each exhibitor profile for email, phone, website, address and socials. Off = names and booths only (faster).

Output Schema

NameRequiredDescriptionDefault
toolYesName of the tool that produced the result.
countYesNumber of records the Actor returned.
itemsYesThe records. Long text fields are shortened to 600 characters.
shownYesNumber of records included in `items` (can be lower than count when the result is long).
truncatedYesTrue when records were left out to keep the result short; ask for fewer items.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.10.1
    • 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"
      +}
  2. Addedv0.4.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the marginal bar is lower. The description still adds substantive behavior: the call runs Apify Actor tacps126/exhibition-scraper on the caller's account, costs about $0.001 per exhibitor, and is capped at $0.5 spend per call. Contact coverage caveats (depends on what the organiser publishes) are also disclosed, though nothing is said about rate limits or failure modes.

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?

A single front-loaded paragraph that leads with the returned lead fields rather than process detail. The long enumerations of show ids and platform names are useful for matching but make the description heavier than strictly necessary.

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 an output schema present, return values need no explanation, and the description covers the remaining gaps: spend cap, per-item pricing, actor dependency, contact-coverage variability, and the changes_only/max_items interaction. An agent has everything needed to call this correctly and predict its cost.

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 goes beyond the schema by explaining that both urls and shows are accepted, that a URL's own show and year are used, and that cost scales with max_items. It adds little on extra_input or changes_only beyond what the schema text already says.

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 names the exact resource (trade show exhibitor lists as B2B leads) and enumerates the returned fields: company, booth/hall, email, phone, website, address, socials, categories. That resource is unmistakably distinct from siblings such as find_companies or find_events, so an agent can select it without opening the schema.

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?

It explains precisely how to invoke the tool: 91 built-in show ids, or any exhibitor-list link/show homepage from named platform families, with the link's own show and year inferred. It does not explicitly name an alternative tool or state when not to use it, which keeps this below a 5.

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