Home / Token cost / Exa Websets

The Exa Websets MCP server costs 3,044 tokens before the first call.

Connect Exa Websets and its 16 tool definitions are loaded into the model's context on every request — 1.5% of a 200k window spent before your agent does anything.

QUICK ANSWER The Exa Websets MCP server's tool definitions consume 3,044 tokens — around the median MCP server (1,905 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS 16 tools · 3,044 tokens · 1.5% of 200k · 0.3% of 1M Method →

What that buys before your agent starts working.

Tool definitions are overhead: they occupy context on every request and compete with your code, documents and conversation history for the same window.

200K WINDOW 1.5%
1M WINDOW 0.3%

Corpus context: Exa Websets ranks #1297 of 3,213 measured MCP servers by definition cost. The median is 1,905 tokens, p90 is 7,952, and the heaviest (Fusionauth) is 183,337 — 92% of a 200k window on its own.

Where the 3,044 tokens go.

Each row is one tool definition as a tools/list entry — name, description and input schema — counted with o200k_base. Average: 190 tokens per tool.

ToolCategoryTokens% of server
create_webset Write 650 21.4%
create_monitor Write 516 17.0%
create_search Write 475 15.6%
create_enrichment Write 410 13.5%
list_webset_items Read 108 3.5%
update_enrichment Write 107 3.5%
update_webset Write 102 3.4%
get_webset Read 86 2.8%
list_websets Read 85 2.8%
delete_enrichment Destructive 79 2.6%
get_item Read 79 2.6%
cancel_enrichment Destructive 74 2.4%
get_search Read 73 2.4%
cancel_search Destructive 72 2.4%
get_enrichment Read 71 2.3%
delete_webset Destructive 57 1.9%

Most agents use a handful of these tools. They pay for all 16.

A PolicyLayer grant exposes only the tools you allow — ungranted definitions are filtered out of the tool list, so they never enter the context window. Estimates below assume typical-weight tools (190 tokens each).

Grant scopeDefinition costReduction
All 16 tools (no gateway) 3,044 tokens
3 granted tools ~571 tokens −81%
5 granted tools ~951 tokens −69%
10 granted tools ~1,903 tokens −38%

Exa Websets token-cost questions.

How many tokens does the Exa Websets MCP server use?+

Its 16 tool definitions total 3,044 tokens — 1.5% of a 200k context window — measured with tiktoken o200k_base over the serialised tools/list payload. Exact counts vary slightly by client and model.

Why does Exa Websets consume tokens before I send a message?+

MCP clients load every connected server's tool definitions — name, description, and input schema — into the model's context so it knows what it can call. That payload is charged against your context window on every request, whether or not a tool is used.

How do I reduce Exa Websets's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Exa Websets to only the tools you allow — ungranted definitions are filtered out of the tool list, so they never enter the context window. A grant of 3 typical tools costs roughly 571 tokens, a 81% reduction.

Does deferred tool loading fix this?+

Partially, in some clients. Claude Code defers MCP tool schemas behind a tool-search step by default, and VS Code has experimental grouping — but you still pay tokens per search and reload, and Cursor, Windsurf and Gemini CLI load definitions upfront. Reducing the exposed tool set cuts the cost in every client.

How these numbers were measured.

01
Serialisation

Each tool is serialised as a tools/list entry — name, description, input schema — from the schemas in the PolicyLayer scan database. Clients differ slightly in framing, so treat counts as close estimates.

02
Tokeniser

tiktoken o200k_base (GPT-4o/o-series). Anthropic's current tokeniser isn't published, so Claude's exact counts will differ; for English text and JSON schemas the totals are close enough to treat these as estimates.

03
Deferred loading

Some clients now defer schema loading (Claude Code's tool search; VS Code experimental grouping). You still pay per search and reload — and Cursor, Windsurf and Gemini CLI load everything upfront.

Computed 07-06-2026 from the PolicyLayer scan database over all 16 catalogued Exa Websets tools. Counts refresh with every site build.

Expose only the tools you use — the rest never enter your context.

A PolicyLayer grant scopes Exa Websets to the tools you actually allow. Ungranted definitions never load, and every call that does run is checked against policy first.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.